[
https://issues.apache.org/jira/browse/HDDS-9125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Siddhant Sangwan reassigned HDDS-9125:
--------------------------------------
Assignee: Siddhant Sangwan
> Decommissioning blocked because of under replicated EC containers
> -----------------------------------------------------------------
>
> Key: HDDS-9125
> URL: https://issues.apache.org/jira/browse/HDDS-9125
> Project: Apache Ozone
> Issue Type: Sub-task
> Components: ECOfflineRecovery, SCM
> Affects Versions: 1.4.0
> Reporter: Siddhant Sangwan
> Assignee: Siddhant Sangwan
> Priority: Major
>
> The situation is well documented under the heading 'Situation 4' in
> https://docs.google.com/document/d/1ebuSwJZkw4wMWWCHinDvRCfNbeFD4kcHMyIN6Q6wD9g/edit?usp=sharing.
> This happens because of limitations in rack scatter policy + replication
> manager flow. One possible solution is implementing "fallback" in the rack
> scatter policy. Along with the doc, this PR is also related -
> https://github.com/apache/ozone/pull/5097.
> An example (summary) of this situation:
> Suppose there are 5 racks and 6 DNs, such that any one rack will have 2 DNs.
> 5 replicas of an EC container are scattered across each of the 5 racks (so
> that there's only 1 replica on each rack). Now, if any of the Datanodes from
> any rack where there's only 1 DN on that rack is decommissioned, under
> replication handling will be blocked.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
