[
https://issues.apache.org/jira/browse/HDDS-1880?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17291355#comment-17291355
]
Hui Fei commented on HDDS-1880:
-------------------------------
In current implements, we don't allow nodes decommission if they are in
maintenance state.
There is the following scenario in production environment.
Based on HDFS experience, if we have a large cluster and we want to
decommission many nodes. Workload will be high if we decommission lots of nodes
at the same time, so we will decommission nodes many times and decommission
tens of nodes at a time. We expect that Other nodes which we want to
decommission are readable but not writable during some nodes in decommissioning
state.
So here suggest that allow it to decommission if one node in maintenance state.
In current implement, we must do that: 1) set maintenance;2)recommission;3)set
decommision. With my suggestion, just do that: 1) set maintenance; 2) set
decommision
Does it make sense? [~sodonnell] [~elek]
> Decommissioning and maintenance mode in Ozone
> ----------------------------------------------
>
> Key: HDDS-1880
> URL: https://issues.apache.org/jira/browse/HDDS-1880
> Project: Apache Ozone
> Issue Type: New Feature
> Components: SCM
> Reporter: Marton Elek
> Assignee: Stephen O'Donnell
> Priority: Major
> Labels: pull-request-available
> Attachments: Decommission and Maintenance Overview.pdf
>
>
> This is the umbrella jira for decommissioning support in Ozone. Design doc
> will be attached soon.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
