[
https://issues.apache.org/jira/browse/HDFS-7877?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14588775#comment-14588775
]
Rajiv Chittajallu commented on HDFS-7877:
-----------------------------------------
* It would be preferable to have a timeout of maintenance state, which would be
higher than {{dfs.namenode.heartbeat.recheck-interval}}.
* Instead of specifying hosts in a file, {{dfs.hosts.maintenance}}, can this be
done via {{dfsadmin}} ? Maintenance mode is an temporary transient state and it
would be simpler to not to track it via files.
bq. That is why we have the case where if a node becomes dead when it is being
decommissioned, it will remains in DECOMMISSION_IN_PROGRESS state until all the
blocks are properly replicated.
If a datanode goes offline while decommissioning, it should be treated as dead
and not be in {{DECOMMISSION_IN_PROGRESS}} state. Re-replicating blocks for
nodes in dead state should be treated with higher priority.
> Support maintenance state for datanodes
> ---------------------------------------
>
> Key: HDFS-7877
> URL: https://issues.apache.org/jira/browse/HDFS-7877
> Project: Hadoop HDFS
> Issue Type: New Feature
> Reporter: Ming Ma
> Attachments: HDFS-7877-2.patch, HDFS-7877.patch,
> Supportmaintenancestatefordatanodes-2.pdf,
> Supportmaintenancestatefordatanodes.pdf
>
>
> This requirement came up during the design for HDFS-7541. Given this feature
> is mostly independent of upgrade domain feature, it is better to track it
> under a separate jira. The design and draft patch will be available soon.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
