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 2025/05/20 15:46:00 UTC

[jira] [Resolved] (HDDS-7096) Clarify locations of on-demand scanning

     [ https://issues.apache.org/jira/browse/HDDS-7096?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ethan Rose resolved HDDS-7096.
------------------------------
    Resolution: Won't Fix

For now we will use the same approach for on-demand container scanning that we do for on-demand volume scanning, which is directly invoking the scanner when issues are encountered.

> Clarify locations of on-demand scanning
> ---------------------------------------
>
>                 Key: HDDS-7096
>                 URL: https://issues.apache.org/jira/browse/HDDS-7096
>             Project: Apache Ozone
>          Issue Type: Sub-task
>            Reporter: Ethan Rose
>            Assignee: Ethan Rose
>            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