You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ozone.apache.org by "Hui Fei (Jira)" <ji...@apache.org> on 2026/06/09 03:58:00 UTC

[jira] [Commented] (HDDS-9595) Investigate QUASI_CLOSED containers with only one UNHEALTHY and empty replica

    [ https://issues.apache.org/jira/browse/HDDS-9595?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18087189#comment-18087189 ] 

Hui Fei commented on HDDS-9595:
-------------------------------

<<Bulk update>>
Apache Ozone 2.2.0 release is in progress. I'm updating all unresolved jiras targeting 2.2.0 to retarget 2.3.0.


> Investigate QUASI_CLOSED containers with only one UNHEALTHY and empty replica
> -----------------------------------------------------------------------------
>
>                 Key: HDDS-9595
>                 URL: https://issues.apache.org/jira/browse/HDDS-9595
>             Project: Apache Ozone
>          Issue Type: Sub-task
>          Components: SCM
>            Reporter: Siddhant Sangwan
>            Priority: Major
>
> We've seen some QUASI_CLOSED containers that have only 1 replica, and that 1 replica is UNHEALTHY and also empty. We need to investigate how the system ends up having such containers, and what to do about them. The solution will likely depend on whether the container is known by SCM to have zero keys. In general, this ties up into the larger problem of the SCM not knowing which containers that appear empty are actually not empty but have missing data, because it doesn't know if there are keys mapped to this container.
> Currently, this is our logic for calling a container empty:
> {code}
>     return container.getState() == HddsProtos.LifeCycleState.CLOSED &&
>         !replicas.isEmpty() &&
>         replicas.stream().allMatch(
>             r -> r.getState() == ContainerReplicaProto.State.CLOSED &&
>                 r.isEmpty());
> {code}



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

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@ozone.apache.org
For additional commands, e-mail: issues-help@ozone.apache.org