[
https://issues.apache.org/jira/browse/HADOOP-1946?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12531248
]
Hadoop QA commented on HADOOP-1946:
-----------------------------------
+1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12366783/du2.patch
against trunk revision r580487.
@author +1. The patch does not contain any @author tags.
javadoc +1. The javadoc tool did not generate any warning messages.
javac +1. The applied patch does not generate any new compiler warnings.
findbugs +1. The patch does not introduce any new Findbugs warnings.
core tests +1. The patch passed core unit tests.
contrib tests +1. The patch passed contrib unit tests.
Test results:
http://lucene.zones.apache.org:8080/hudson/job/Hadoop-Patch/850/testReport/
Findbugs warnings:
http://lucene.zones.apache.org:8080/hudson/job/Hadoop-Patch/850/artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Checkstyle results:
http://lucene.zones.apache.org:8080/hudson/job/Hadoop-Patch/850/artifact/trunk/build/test/checkstyle-errors.html
Console output:
http://lucene.zones.apache.org:8080/hudson/job/Hadoop-Patch/850/console
This message is automatically generated.
> du should be not called on every heartbeat
> ------------------------------------------
>
> Key: HADOOP-1946
> URL: https://issues.apache.org/jira/browse/HADOOP-1946
> Project: Hadoop
> Issue Type: Bug
> Components: dfs
> Affects Versions: 0.15.0
> Reporter: Konstantin Shvachko
> Assignee: Hairong Kuang
> Priority: Blocker
> Fix For: 0.15.0
>
> Attachments: du.patch, du.patch, du2.patch
>
>
> Data-nodes run very slow. The reason is that du is executed on each and every
> heartbeat.
> Looks like the condition in DU.getUsed(), which triggers the refresh of
> cached values, should be reversed.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
