[
https://issues.apache.org/jira/browse/HADOOP-1627?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12613137#action_12613137
]
Hadoop QA commented on HADOOP-1627:
-----------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12385806/HADOOP-1627.patch
against trunk revision 676069.
+1 @author. The patch does not contain any @author tags.
-1 tests included. The patch doesn't appear to include any new or modified
tests.
Please justify why no tests are needed for this patch.
+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 release audit. The applied patch does not increase the total number of
release audit warnings.
+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/2848/testReport/
Findbugs warnings:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/2848/artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Checkstyle results:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/2848/artifact/trunk/build/test/checkstyle-errors.html
Console output:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/2848/console
This message is automatically generated.
> DFSAdmin incorrectly reports cluster data.
> ------------------------------------------
>
> Key: HADOOP-1627
> URL: https://issues.apache.org/jira/browse/HADOOP-1627
> Project: Hadoop Core
> Issue Type: Improvement
> Components: dfs
> Affects Versions: 0.13.0
> Reporter: Konstantin Shvachko
> Assignee: Raghu Angadi
> Priority: Minor
> Fix For: 0.19.0
>
> Attachments: HADOOP-1627.patch
>
>
> This is what dfsadmin -report currently prints.
> {code}
> hadoop:504>bin/hadoop dfsadmin -report
> Total raw bytes: 1705541296128 (1.55 TB)
> Used raw bytes: 1388220184240 (1.26 TB)
> % used: 81.39%
> Total effective bytes: 8388847 (8.00 MB)
> Effective replication multiplier: 165484.0270945459
> -------------------------------------------------
> Datanodes available: 3
> Name: alive.node.1:50077
> State : In Service
> Total raw bytes: 60003868672 (55.88 GB)
> Used raw bytes: 21500184005 (20.02 GB)
> % used: 35.83%
> Last contact: Tue Jul 17 19:58:00 PDT 2007
> Name: alive.node.2:50077
> State : In Service
> Total raw bytes: 1645537427456 (1.49 TB)
> Used raw bytes: 1366720000235 (1.24 TB)
> % used: 83.05%
> Last contact: Tue Jul 17 19:58:01 PDT 2007
> Name: dead.node:50077
> State : In Service
> Total raw bytes: 0 (0.0 k)
> Used raw bytes: 0 (0.0 k)
> % used: NaN%
> Last contact: Wed Nov 01 12:18:10 PST 2006
> {code}
> # "Effective replication multiplier" is confusing and prints a strange number
> # Datanodes available: 3 - should count only live nodes.
> # A dead node "State" should not be "In Service".
> # "% used:" should not print "NaN%"
> # We should synchronize dfsadmin reporting with the what we report via the
> web UI.
> Field names and numbers should be the same.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
