hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ming Ma (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-7877) Support maintenance state for datanodes
Date Sat, 11 Feb 2017 22:08:42 GMT

    [ https://issues.apache.org/jira/browse/HDFS-7877?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15862549#comment-15862549

Ming Ma commented on HDFS-7877:

Thanks [~manojg]. Good point. What you suggested makes sense. The reason we don't have this
requirement in our production is probably because we only put nodes in one upgrade domain
into maintenance at a time; after one batch is done, move to the next upgrade domain. Thus
no two replicas will be put to maintenance at the same time.

To confirm, given we will still allow applications to create blocks with smaller replication
factor than {{dfs.namenode.maintenance.replication.min}}, the transition policy from {{ENTERING_MAINTENANCE}}
to {{IN_MAINTENANCE}} becomes the # of live replicas >= min({{dfs.namenode.maintenance.replication.min}},
replication factor).

> Support maintenance state for datanodes
> ---------------------------------------
>                 Key: HDFS-7877
>                 URL: https://issues.apache.org/jira/browse/HDFS-7877
>             Project: Hadoop HDFS
>          Issue Type: New Feature
>          Components: datanode, namenode
>            Reporter: Ming Ma
>            Assignee: Ming Ma
>         Attachments: HDFS-7877-2.patch, HDFS-7877.patch, Supportmaintenancestatefordatanodes-2.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

To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org

View raw message