You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ozone.apache.org by "Ethan Rose (Jira)" <ji...@apache.org> on 2021/10/20 20:39:09 UTC
[jira] [Updated] (HDDS-3509) Closing container with unhealthy
replica on open pipeline
[ https://issues.apache.org/jira/browse/HDDS-3509?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ethan Rose updated HDDS-3509:
-----------------------------
Target Version/s: 1.3.0 (was: 1.2.0)
I am managing the 1.2.0 release and we currently have more than 600 issues targeted for 1.2.0. I am moving the target field to 1.3.0.
If you are actively working on this jira and believe this should be targeted for the 1.2.0 release, Please reach out to me via Apache email or Slack.
> Closing container with unhealthy replica on open pipeline
> ---------------------------------------------------------
>
> Key: HDDS-3509
> URL: https://issues.apache.org/jira/browse/HDDS-3509
> Project: Apache Ozone
> Issue Type: Bug
> Components: Ozone Datanode
> Affects Versions: 0.5.0
> Reporter: Nilotpal Nandi
> Assignee: Lokesh Jain
> Priority: Major
>
> When a container replica of an OPEN container is marked as UNHEALTHY, SCM tries to close the container.
> If the pipeline is still healthy, we try to close the container via Ratis.
> We could run into a scenario where the datanode which marked the container replica as UNHEALTHY is the pipeline leader. In such case that datanode (leader) should process the close container command even though the container replica is in UNHEALTHY state.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@ozone.apache.org
For additional commands, e-mail: issues-help@ozone.apache.org