[
https://issues.apache.org/jira/browse/HDFS-7877?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14594075#comment-14594075
]
Ming Ma commented on HDFS-7877:
-------------------------------
Thanks [~rajive] for your input! I also discussed with [~rawk].
* Support for timeout. Sounds like folks prefer to have HDFS support that. That
makes sense. Value of -1 could mean no timeout. In addition, based on current
scenarios it seems we don't need to support per-host timeout; instead we can
use some global timeout value.
* Support for persistence. If we don't put the maintenance files into some
file, it will be lost after NN restart. In other words, the node will be
transitioned out of maintenance state upon NN restart. So from admin point of
view, the node could be transitioned out of maintenance state prior to the
timeout. Are we ok with such possible inconsistency?
* If the node should be taken of DECOMMISSIONING when the node becomes dead.
Admin state is separate from the liveness state. The reason the node is kept in
DECOMMISSIONING state is to address data reliability issue. HDFS-6791 has more
details.
> 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)
