[jira] [Commented] (HDDS-6549) Do not mark contianer replica as unhealthy on write failure

["Ethan Rose (Jira)" <ji...@apache.org>]

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

Ethan Rose commented on HDDS-6549:
----------------------------------

In the context of the container scanner, this means that only the scanner should mark containers as unhealthy after doing a full data scan. Containers will be scanned when a client gets an error since HDDS-7095

> Do not mark contianer replica as unhealthy on write failure
> -----------------------------------------------------------
>
>                 Key: HDDS-6549
>                 URL: https://issues.apache.org/jira/browse/HDDS-6549
>             Project: Apache Ozone
>          Issue Type: Sub-task
>            Reporter: Hanisha Koneru
>            Priority: Major
>
> If an operation fails on an open/ closing container on a DN, it is marked unhealthy so that subsequent write transactions also fail. The container itself is marked for closing by sending a request to SCM. 
> Even if a write failed, other data in the container could be intact. Marking containers unhealthy should be a conservative operation. If let's say write fails on all replicas of a container, then all the replicas would be marked unhealthy. HDDS-6447 will ensure that replicas are not deleted if all the replicas are in unhealthy state. Irrespective of that, a container should not be marked as unhealthy when there is readable uncorrupted data in it.
> Currently, we cannot mark the container with any other state as all container state changes are initiated from the SCM. If we quasi close a container replica, instead of marking it unhealthy, when there is a write failure, then all the state transition logic in SCM would also have to be changed/updated.



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