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:58:00 UTC
[jira] [Commented] (HDDS-8785) More graceful handling of recoverable volume failures
[ https://issues.apache.org/jira/browse/HDDS-8785?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17952907#comment-17952907 ]
Ethan Rose commented on HDDS-8785:
----------------------------------
One option is to use a different metric for this, which could be handled differently by an alerting system. For example {{NumFailedVolumes}} gets incremented for each volume failure regardless of the cause, but another {{NumMisconfiguredVolumes}} or similar also gets incremented when a volume is failed due to filesystem issues like permissions.
> More graceful handling of recoverable volume failures
> -----------------------------------------------------
>
> Key: HDDS-8785
> URL: https://issues.apache.org/jira/browse/HDDS-8785
> Project: Apache Ozone
> Issue Type: Sub-task
> Reporter: Ethan Rose
> Priority: Major
>
> Some issues with volumes are recoverable by admins, like incorrect permissions or running out of file descriptors. Right now the only way we have to alert admins and fix the problem is fail the volume, which can trigger unnecessary replication since the data may still be good, we just cannot read it. It would be good to have a better way to alert about the issue and give it a chance to be fixed without triggering Ozone replication.
--
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