[
https://issues.apache.org/jira/browse/HDFS-12810?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16255214#comment-16255214
]
Virajith Jalaparti commented on HDFS-12810:
-------------------------------------------
Thanks for posting a fix [~hanishakoneru]. While this fix solves this
particular case, is there a reason why the value of 0 "gets lost" from
{{dfshealth.js}} to {{dfshealth.html}} ({{b.capacityRemaining}} has a value of
0 in {{dfshealth.js}} but {{value.capacityRemaining}} doesn't retain this value
in {{dfshealth.html}}) ? I suspect this might be something to do with the call
to {{render()}} in {{dfshealth.js}}.
> Under "DFS Storage Types", the Namenode Web UI doesn't display the
> capacityRemaining correctly when it is 0.
> ------------------------------------------------------------------------------------------------------------
>
> Key: HDFS-12810
> URL: https://issues.apache.org/jira/browse/HDFS-12810
> Project: Hadoop HDFS
> Issue Type: Bug
> Reporter: Virajith Jalaparti
> Assignee: Hanisha Koneru
> Attachments: HDFS-12810.001.patch
>
>
> When the {{capacityRemaining}} for a StorageType is 0, the Namenode's Web UI
> displays an empty string ("()") instead of "0 (0%)".
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
