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

ASF GitHub Bot updated HDDS-9165:
---------------------------------
    Labels: pull-request-available  (was: )

> Exclude empty CLOSED containers in ContainerSafeModeRule
> --------------------------------------------------------
>
>                 Key: HDDS-9165
>                 URL: https://issues.apache.org/jira/browse/HDDS-9165
>             Project: Apache Ozone
>          Issue Type: Bug
>          Components: SCM
>            Reporter: Nandakumar
>            Assignee: Sadanand Shenoy
>            Priority: Major
>              Labels: pull-request-available
>
> The containers which are created in SCM and never got created on the 
> datanodes (allocated block discarded by the client) and moved to {{CLOSING}} 
> state during pipeline deletion and are marked as {{CLOSED}} by HDDS-7882.
> When SCM is restarted before those containers are deleted, we end up having 
> {{CLOSED}} (empty) containers in SCM but no corresponding replicas on any of 
> the datanodes. This is causing the SCM to be stuck in {{{}safemode{}}}.



--
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