[
https://issues.apache.org/jira/browse/HDFS-9391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15753127#comment-15753127
]
Manoj Govindassamy commented on HDFS-9391:
------------------------------------------
Thanks for the detailed comments [~mingma]. Much appreciated.
{{FSNameSystem#getDecomNodes}}
{quote}
If we really want to separately account for
all-3-replicas-being-decommissioned, we can keep the strict semantics and add a
new property "outOfServiceOnlyReplicas" to account for both types. To enable
that, we will need to track each type separately in LeavingServiceStatus.
{quote}
{quote}
// TODO use another property name for outOfServiceOnlyReplicas.
.put("decommissionOnlyReplicas",
node.getLeavingServiceStatus().getOutOfServiceOnlyReplicas())
{quote}
Risk indicator including all probable failures does sounds good. Except, the
other page which shows more details on the Decommissioning Nodes will not tally
with this number. So, I would like {{decommissionOnlyReplicas}} property to
capture decommission related ones only and additionally have another property
{{outOfServiceOnlyReplicas}} capturing all. Yes, we will have to extend
{{LeavingServiceStatus}} to include all these numbers, but looks straight
forward and useful to me. Will go with this approach.
All other items totally makes sense. Thanks.
> Update webUI/JMX/fsck to display maintenance state info
> -------------------------------------------------------
>
> Key: HDFS-9391
> URL: https://issues.apache.org/jira/browse/HDFS-9391
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Reporter: Ming Ma
> Assignee: Manoj Govindassamy
> Attachments: Maintenance webUI.png
>
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
