[
https://issues.apache.org/jira/browse/HDDS-13976?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan Andika updated HDDS-13976:
-------------------------------
Summary: Use last pipeline leader ID to handle quasi closed stuck
containers (was: Use last pipeline leader ID handle quasi closed stuck
containers)
> Use last pipeline leader ID to handle quasi closed stuck containers
> -------------------------------------------------------------------
>
> Key: HDDS-13976
> URL: https://issues.apache.org/jira/browse/HDDS-13976
> Project: Apache Ozone
> Issue Type: Sub-task
> Reporter: Ivan Andika
> Priority: Major
>
> This is simply an idea.
> Currently, we mainly use BCSID and originNodeId to check whether we should
> close a container. However, these two information are sometimes not enough to
> ensure that the close quasi closed stuck containers.
> It might be possible for us to use the last leader ID and use the Raft leader
> guarantees (i.e. highest committed index) to add more cases where container
> can still be closed if the origin node ID of the replicas are equal to last
> leader ID (despite the <= 3 unique origin node ID).
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
