[
https://issues.apache.org/jira/browse/HDFS-9391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15804018#comment-15804018
]
Manoj Govindassamy commented on HDFS-9391:
------------------------------------------
Got your point. Thats right. {{processBlocksInternal}} goes over block by block
and gets {{NumberReplicas}} for each of the block. The {{NumberReplicas}} thus
returned will have both decommissioning and maintenance check passing through
for the case1 we discussed. Thanks a lot for detailed discussion with example
cases on this.
So, are we good with patch v02 w.r.t Decommissioning and EnteringMaintenance
page stats ?
If you are ok with this, I will incorporate the other open review comments like
the following and upload patch v03
* leaving "decommissioned" attr in FSNameSystem#getDeadNodes() as is
* removal decommission check in {{getMaintenanceOnlyReplicas}}
* addition of {{dfshealth-node-down-maintenance}} in DN page
> Update webUI/JMX to display maintenance state info
> --------------------------------------------------
>
> Key: HDFS-9391
> URL: https://issues.apache.org/jira/browse/HDFS-9391
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Affects Versions: 3.0.0-alpha1
> Reporter: Ming Ma
> Assignee: Manoj Govindassamy
> Attachments: HDFS-9391-MaintenanceMode-WebUI.pdf, HDFS-9391.01.patch,
> HDFS-9391.02.patch, 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]
