[
https://issues.apache.org/jira/browse/HDDS-14995?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated HDDS-14995:
----------------------------------
Labels: pull-request-available (was: )
> [Docs] Explain the datanode decommissioning transition criteria
> ---------------------------------------------------------------
>
> Key: HDDS-14995
> URL: https://issues.apache.org/jira/browse/HDDS-14995
> Project: Apache Ozone
> Issue Type: Task
> Components: documentation
> Reporter: Wei-Chiu Chuang
> Priority: Major
> Labels: pull-request-available
>
> Siimlar to HDDS-14994, give a succinct explanation of the transition
> criteria, but for datanode decommission.
>
> The main difference is: Decommissioning is strict: Because the node is never
> coming back, Ozone treats it as if the data on that node is already gone. It
> won't let the node
> finish decommissioning until the cluster is back to "Perfect Health"
> (3/3 replicas or 9/9 shards) without that node.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]