[jira] [Commented] (HDDS-7096) Clarify failures that cause a container to be marked unhealthy

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

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

Ethan Rose commented on HDDS-7096:
----------------------------------

A more involved solution using aspect oriented programming is proposed [here|https://github.com/apache/ozone/pull/3788#discussion_r993694138]. This could be applied to the existing volume scanner as well.

> Clarify failures that cause a container to be marked unhealthy
> --------------------------------------------------------------
>
>                 Key: HDDS-7096
>                 URL: https://issues.apache.org/jira/browse/HDDS-7096
>             Project: Apache Ozone
>          Issue Type: Sub-task
>            Reporter: Ethan Rose
>            Assignee: Szabolcs Gál
>            Priority: Major
>
> Currently it is difficult to tell whether an IOException will cause a container to be marked unhealthy or not. The exception must be traced all the way up the stack checking each frame to see if the caller is moving the container to unhealthy. The goal of this jira is to clarify which operations cause a container to be marked unhealthy at the code level.
> In [HDDS-7095|https://issues.apache.org/jira/browse/HDDS-7095] a general place was given for on-demand scanning. Clarify and move the places where on-demand scans are added if necessary.



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