[
https://issues.apache.org/jira/browse/HDFS-4924?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13770103#comment-13770103
]
Chris Nauroth commented on HDFS-4924:
-------------------------------------
Blocker indicates that a specific Apache release version (the target version
field in the issue) can't be published until this is resolved. Usually it's
due to something catastrophic like data loss or unintended
backwards-incompatibility or regression of existing functionality. Certainly
this patch provides a helpful feature, but is it a blocker?
There is no target version defined for this issue, so if it is a blocker, then
it's unclear which release needs to be blocked.
> Show NameNode state on dfsclusterhealth page
> --------------------------------------------
>
> Key: HDFS-4924
> URL: https://issues.apache.org/jira/browse/HDFS-4924
> Project: Hadoop HDFS
> Issue Type: Improvement
> Components: federation
> Affects Versions: 2.1.0-beta
> Reporter: Lohit Vijayarenu
> Assignee: Lohit Vijayarenu
> Priority: Blocker
> Attachments: HDFS-4924.trunk.1.patch
>
>
> dfsclusterhealth.jsp shows summary of multiple namenodes in cluster. With
> federation combined with HA it becomes difficult to quickly know the state of
> NameNodes in the cluster. It would be good to show if NameNode is
> Active/Standy on summary page.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
