[
https://issues.apache.org/jira/browse/HDDS-9657?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stephen O'Donnell updated HDDS-9657:
------------------------------------
Summary: Mark recovering containers unhealthy after DN restart (was: EC:
When Coordinator DN doing reconstruction, restart of target DN can lead to SCM
crash)
> Mark recovering containers unhealthy after DN restart
> -----------------------------------------------------
>
> Key: HDDS-9657
> URL: https://issues.apache.org/jira/browse/HDDS-9657
> Project: Apache Ozone
> Issue Type: Bug
> Affects Versions: 1.3.0
> Reporter: Uma Maheswara Rao G
> Assignee: Saketa Chalamchala
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.4.0
>
>
> Currently DN restart cleanup the RECOVERY containers. Ideally post cleanup of
> recovering containers, if coordinator continue to write chunks, it should
> just fail. But write chunk will create container if it's not exist. It can
> simply create OPEN container with replication index 0 as simple write chunk
> request will not have full EC context. In the past when
> RecoveringContainerScrubber deleted the recovering containers, write chunk
> introduced the replica index 0 container (HDDS-7462). So, similar issue can
> happen due to restart time recovery containers cleanup.
> If DNs reports replica index 0 for EC containers, SCM thinks system went into
> unexpected conditions and it will crash.
> Proposal: we should just move recovering container into UNHEALTHY state
> instead of deleting them.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
