You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ozone.apache.org by "Priyesh K (Jira)" <ji...@apache.org> on 2026/02/27 08:30:00 UTC

[jira] [Commented] (HDDS-11693) SCM Safemode Improvements

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

Priyesh K commented on HDDS-11693:
----------------------------------

Hi [~nanda] ,

There are multiple tickets proposing the removal of datanode report processing and instead relying on the *PipelineManager* and *NodeManager* to determine the required status.

However, currently the {{SafeModeExitRule}} triggers its validation logic upon receiving datanode reports. If we are planning to remove the processing logic from the safe mode rule validations, I would like to understand what the new trigger point for these validations will be.

Is there any existing design documentation related to this refactoring? Also, has there been any prior design discussion or background context around this change that I can refer to?

Please let me know if there are any references or documents available.

> SCM Safemode Improvements
> -------------------------
>
>                 Key: HDDS-11693
>                 URL: https://issues.apache.org/jira/browse/HDDS-11693
>             Project: Apache Ozone
>          Issue Type: Improvement
>          Components: SCM
>            Reporter: Nandakumar
>            Assignee: Nandakumar
>            Priority: Major
>
> This parent Jira tracks the SCM Safemode improvements.
> Currently, the Safemode Rule validation is driven by processing of reports sent by Datanodes, this is unnecessary and this also introduces additional complexity as every rule is maintaining the same information that the NodeManager, PipelineManager & the ContainerManager are maintaining.
> Since the information about Datanodes/Pipelines/Containers are maintained at two different places, this can go out of sync and introduce bugs into safemode logic. (eg: HDDS-5263)
> We will move to a simpler model where the SafemodeManager will not care about report processing (Safemode Rules will not process any Datanode Reports) but check NodeManager, PipelineManager and ContainerManager to validate the exit rule.
> With this change the Safemode logic will become simple and easy to follow.



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