[
https://issues.apache.org/jira/browse/HDDS-15138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aryan Gupta updated HDDS-15138:
-------------------------------
Description:
This patch switches SCM safemode handling to the new EC approach.
When default replication is EC, SCM now uses a dedicated
{{ECMinDataNodeSafeModeRule}} to check if enough healthy DataNodes are
available ({{{}data + parity{}}}) before safemode exit.
A new config flag controls whether {{BackgroundPipelineCreator}} should create
{{RATIS/THREE}} pipelines in EC-default clusters:
* {{ozone.scm.pipeline.creation.ec.ratis.three.enabled=true}} -> create
RATIS/THREE pipelines in background
* {{false}} -> do not create background pipelines for EC-default
For RATIS-default clusters, behavior stays the same as before.
Tests were updated to match this behavior:
* added tests for the new EC DN safemode rule
* added tests for EC-default + flag true/false behavior
was:
This patch switches SCM safemode handling to the new EC approach.
When default replication is EC, SCM now uses a dedicated
{{ECMinDataNodeSafeModeRule}} to check if enough healthy DataNodes are
available ({{{}data + parity{}}}) before safemode exit. We no longer rely on EC
pipeline health checks for this.
A new config flag controls whether {{BackgroundPipelineCreator}} should create
{{RATIS/THREE}} pipelines in EC-default clusters:
* {{ozone.scm.pipeline.creation.ec.ratis.three.enabled=true}} -> create
RATIS/THREE pipelines in background
* {{false}} -> do not create background pipelines for EC-default
For RATIS-default clusters, behavior stays the same as before.
Tests were updated to match this behavior:
* added tests for the new EC DN safemode rule
* added tests for EC-default + flag true/false behavior
* removed old tests tied to the previous EC pipeline-validation approach
> SCM safemode pipeline rules should honor default EC replication config
> ----------------------------------------------------------------------
>
> Key: HDDS-15138
> URL: https://issues.apache.org/jira/browse/HDDS-15138
> Project: Apache Ozone
> Issue Type: Improvement
> Reporter: Aryan Gupta
> Assignee: Aryan Gupta
> Priority: Major
> Labels: pull-request-available
>
> This patch switches SCM safemode handling to the new EC approach.
> When default replication is EC, SCM now uses a dedicated
> {{ECMinDataNodeSafeModeRule}} to check if enough healthy DataNodes are
> available ({{{}data + parity{}}}) before safemode exit.
> A new config flag controls whether {{BackgroundPipelineCreator}} should
> create {{RATIS/THREE}} pipelines in EC-default clusters:
> * {{ozone.scm.pipeline.creation.ec.ratis.three.enabled=true}} -> create
> RATIS/THREE pipelines in background
> * {{false}} -> do not create background pipelines for EC-default
> For RATIS-default clusters, behavior stays the same as before.
> Tests were updated to match this behavior:
> * added tests for the new EC DN safemode rule
> * added tests for EC-default + flag true/false behavior
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
