[
https://issues.apache.org/jira/browse/HDDS-7640?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stephen O'Donnell resolved HDDS-7640.
-------------------------------------
Fix Version/s: 1.4.0
Resolution: Fixed
> EC: UNHEALTHY replicas not replaced by healthy replicas from a CLOSED
> container by RM
> -------------------------------------------------------------------------------------
>
> Key: HDDS-7640
> URL: https://issues.apache.org/jira/browse/HDDS-7640
> Project: Apache Ozone
> Issue Type: Bug
> Components: ECOfflineRecovery, SCM
> Affects Versions: 1.3.0
> Reporter: Jyotirmoy Sinha
> Assignee: Siddhant Sangwan
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.4.0
>
>
> Scenario :
> In a cluster(13 datanodes) having bucket of EC replication RS-3-2-1024K, for
> a container of a key which is in CLOSED state, 2 of the replicas in the
> cluster are made UNHEALTHY.
> {code:java}
> Replica Index 1: Closed
> Replica Index 2: Unhealthy
> Replica Index 3: Closed
> Replica Index 4: Unhealthy
> Replica Index 5: Closed{code}
> Expected behaviour - The container should be identified as under replicated
> due to the unhealthy containers. Once is it fully replicated, the unhealthy
> containers should be removed.
> Observed behaviour - The UNHEALTHY replicas are still in the container after
> 12 hours and the under replication is not identified or fixed.
> The reason is that the container is handled in
> ClosedWithMismatchedReplicasHandler as all replica states does not match the
> the container state (CLOSED with 2 UNHEALTHY). However we should not consider
> UNHEALTHY in ClosedWithMismatchedReplicasHandler, as its a special state. Its
> more intended for a CLOSED container with OPEN or CLOSING replicas.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
