[
https://issues.apache.org/jira/browse/HADOOP-2816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12632419#action_12632419
]
Hairong Kuang commented on HADOOP-2816:
---------------------------------------
1. FSDataSet.java: getCapacity() should make sure that it does not return a
negative number.
2. FSNamesystem.java: In getCapacityUsedPercent(), used space should be divided
by the present capacity. FSNamesystem probably should not have this public
method since it is only used in a test.
3. DatanodeInfo.getDfsUsedPercent should check the case that the present
capacity is zero. Again, I do not think this public method needs to add to the
class since it is only used in webUI and the test.
4. In webUI, better to rename "Total Capacity" to be "Configured Capacity" to
show that it is different from the old definition.
5. Since the capacity field in the heartbeat has a new definition, should we
bump up the DatanodeProtocol version?
> Cluster summary at name node web has confusing report for space utilization
> ---------------------------------------------------------------------------
>
> Key: HADOOP-2816
> URL: https://issues.apache.org/jira/browse/HADOOP-2816
> Project: Hadoop Core
> Issue Type: Improvement
> Components: dfs
> Reporter: Robert Chansler
> Assignee: Suresh Srinivas
> Fix For: 0.19.0
>
> Attachments: HADOOP-2816.patch
>
>
> In one example:
> Cluster Summary
> Capacity : 1.15 PB
> DFS Remaining : 192 TB
> DFS Used : 717 TB
> DFS Used% : 62 %
> Why is Capacity not equal Used plus Remaining?
> (The answer is that there is an estimated reserve for local files.)
> The presentation should be easily understood by the user.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
