[jira] [Resolved] (HDDS-11843) Enhance DataNodeSafeModeRule to Use Pipeline DN List

["Shilun Fan (Jira)" <ji...@apache.org>]

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

Shilun Fan resolved HDDS-11843.
-------------------------------
    Resolution: Works for Me

> Enhance DataNodeSafeModeRule to Use Pipeline DN List
> ----------------------------------------------------
>
>                 Key: HDDS-11843
>                 URL: https://issues.apache.org/jira/browse/HDDS-11843
>             Project: Apache Ozone
>          Issue Type: Improvement
>          Components: SCM
>            Reporter: Shilun Fan
>            Assignee: Shilun Fan
>            Priority: Major
>              Labels: pull-request-available
>
> Currently, the *DataNodeSafeModeRule* in SCM requires users to manually configure the number of DataNodes in the cluster using the setting {{{}hdds.scm.safemode.min.datanode{}}}, with a default value of 1. If not configured, this value defaults to 1. However, since clusters are frequently scaled and the number of active DataNodes is uncertain, relying on a fixed value to determine whether SafeMode conditions are met is not reliable.
> To address this issue, we propose a new rule: allowing *DataNodeSafeModeRule* to retrieve the DataNode list from the registered Pipeline and use a configurable ratio to dynamically calculate the required number of DataNodes. This will provide a more accurate way to determine when the system can exit SafeMode.



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