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

["Shahrukh Khan (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/AMBARI-21731?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Shahrukh Khan updated AMBARI-21731:
-----------------------------------
    External issue URL: https://hortonworks.jira.com/browse/RMP-9584
     External issue ID: RMP-9584

> 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
>              Labels: datanode, decommision, hdfs, rolling, rolling_decommision
>
> 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)