You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ambari.apache.org by "Shahrukh Khan (JIRA)" <ji...@apache.org> on 2017/08/16 06:58:00 UTC

[jira] [Created] (AMBARI-21731) Rolling Decommission of HDFS Datanodes

Shahrukh Khan created AMBARI-21731:
--------------------------------------

             Summary: Rolling Decommission of HDFS Datanodes
                 Key: AMBARI-21731
                 URL: https://issues.apache.org/jira/browse/AMBARI-21731
             Project: Ambari
          Issue Type: New Feature
          Components: ambari-server
    Affects Versions: 2.5.1
            Reporter: Shahrukh Khan


Implement feature of Rolling Decommission for HDFS Datanodes.

Use "Under-Replicated Blocks" as parameter for Rolling Decommission, Instead of Wait Time.


E.g. - To decommission 100 HDFS Datanodes - with rolling decommission of 3 nodes at a time, a batch of decommission should trigger when a threshold of - "Minimum number of Under-Replicated Blocks" has reached.

*Note - Minimum Threshold of - "Under-Replicated Blocks" has to be taken care so that we don't end up in a situation with huge load on HDFS Namenode and high number of Under Replicated Blocks - Specially with Datanodes of huge Data size ( ~ TB )



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)