[ 
https://issues.apache.org/jira/browse/HDDS-9763?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Siddhant Sangwan updated HDDS-9763:
-----------------------------------
    Description: 
When all replicas of a CLOSED container are UNHEALTHY and more than replication 
factor, the container is reported as over replicated but not queued to the over 
replication queue. This jira will fix this and also define clear and separate 
responsibilities to RatisReplicationCheckHandler and 
RatisUnhealthyReplicationCheckHandler to avoid confusion.

This problem only affects the new ReplicationManager.

  was:When all replicas of a CLOSED container are UNHEALTHY and more than 
replication factor, the container is reported as over replicated but not queued 
to the over replication queue. This jira will fix this and also define clear 
and separate responsibilities to RatisReplicationCheckHandler and 
RatisUnhealthyReplicationCheckHandler to avoid confusion.


> Over Replication Check of all UNHEALTHY replicas is broken 
> -----------------------------------------------------------
>
>                 Key: HDDS-9763
>                 URL: https://issues.apache.org/jira/browse/HDDS-9763
>             Project: Apache Ozone
>          Issue Type: Sub-task
>          Components: SCM
>            Reporter: Siddhant Sangwan
>            Assignee: Siddhant Sangwan
>            Priority: Critical
>
> When all replicas of a CLOSED container are UNHEALTHY and more than 
> replication factor, the container is reported as over replicated but not 
> queued to the over replication queue. This jira will fix this and also define 
> clear and separate responsibilities to RatisReplicationCheckHandler and 
> RatisUnhealthyReplicationCheckHandler to avoid confusion.
> This problem only affects the new ReplicationManager.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to