[
https://issues.apache.org/jira/browse/HADOOP-4430?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12640757#action_12640757
]
Hadoop QA commented on HADOOP-4430:
-----------------------------------
+1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12392389/HADOOP-4430.patch
against trunk revision 705831.
+1 @author. The patch does not contain any @author tags.
+1 tests included. The patch appears to include 3 new or modified tests.
+1 javadoc. The javadoc tool did not generate any warning messages.
+1 javac. The applied patch does not increase the total number of javac
compiler warnings.
+1 findbugs. The patch does not introduce any new Findbugs warnings.
+1 Eclipse classpath. The patch retains Eclipse classpath integrity.
+1 core tests. The patch passed core unit tests.
+1 contrib tests. The patch passed contrib unit tests.
Test results:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/3492/testReport/
Findbugs warnings:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/3492/artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Checkstyle results:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/3492/artifact/trunk/build/test/checkstyle-errors.html
Console output:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/3492/console
This message is automatically generated.
> Namenode Web UI capacity report is inconsistent with Balancer
> -------------------------------------------------------------
>
> Key: HADOOP-4430
> URL: https://issues.apache.org/jira/browse/HADOOP-4430
> Project: Hadoop Core
> Issue Type: Bug
> Components: dfs
> Affects Versions: 0.19.0
> Reporter: Suresh Srinivas
> Assignee: Suresh Srinivas
> Priority: Blocker
> Fix For: 0.19.0
>
> Attachments: HADOOP-4430.patch, HADOOP-4430.patch, HADOOP-4430.patch
>
>
> Solution to 2816 changed
> - Total Capacity definition from (the disk space of all data directories) to
> (the disk space of all the data directories - the reserved space)
> - We added a new element Present Capacity to the report. It is set to (Used
> Capacity + Remaining Capacity)
> - We changed the Used Percentage reported from (Used Capacity)/(Total
> Capacity) to (Used Capacity)/(Present Capacity)
> - All these changes are displayed on Namenode Web UI.
> Balancer functionality
> Balancer script is started with a threshold parameter. It tries to move the
> blocks from the nodes that have Used % that is more than (Cluster average +
> threshold) to the nodes that have less than (Cluster average - threshold).
> Essentially balancer gets all the datanodes used % to with in (the Cluster
> average +/- threshold).
> Inconsistencies due to the change in 2816
> When MapReduce jobs are run, temporary files are generated. This eats away a
> lot of space from Present Capacity. The difference between the Total Capacity
> and the Present Capacity can be huge. Currently balancer computes Used
> Percentage based (Used Capacity)/(Total Capacity). The Used % the balancer
> uses could be significantly different from Used % displayed on the Namenode
> Web UI. When balancer is done balancing, the Namenode Used % might still
> appear unbalanced.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
