[
https://issues.apache.org/jira/browse/HDDS-14551?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated HDDS-14551:
----------------------------------
Labels: pull-request-available (was: )
> Container state and sequence id doesn't match with empty replica can cause
> abnormal behaviour
> ---------------------------------------------------------------------------------------------
>
> Key: HDDS-14551
> URL: https://issues.apache.org/jira/browse/HDDS-14551
> Project: Apache Ozone
> Issue Type: Bug
> Reporter: Ashish Kumar
> Assignee: Ashish Kumar
> Priority: Major
> Labels: pull-request-available
>
> In some old environment or due to certain issue below scenario can happen
> Assume ratis container with below 3 replica
> Replica1 BCSID:0 (Due to volume failure or some issue on DN)
> Replica2 BCSID:10
> Replica3:BCSID:10
> All 3 replica reported to SCM, SCM updates its BCSID as 10.
> Replica1 with BCSID 0 moved from QUASI CLOSE–>CLOSED(As in old version we do
> based on majority)
> Replica2 and Replica3 went down or don’t report to SCM now.
> Replica1 moved from CLOSED–>DELETED.
> SCM container state updated from CLOSED–>DELETED but container sequence id
> remained at 10.
> If this scenario happens SCM should not update container state as it can lead
> to other issue and can cause data loss.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
