You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ozone.apache.org by "Wei-Chiu Chuang (Jira)" <ji...@apache.org> on 2026/05/19 23:22:00 UTC

[jira] [Created] (HDDS-15326) If SCM outofservice.limit.factor is > 10, it resets back to 2

Wei-Chiu Chuang created HDDS-15326:
--------------------------------------

             Summary: If SCM outofservice.limit.factor is > 10, it resets back to 2
                 Key: HDDS-15326
                 URL: https://issues.apache.org/jira/browse/HDDS-15326
             Project: Apache Ozone
          Issue Type: Bug
            Reporter: Wei-Chiu Chuang


hdds.datanode.replication.outofservice.limit.factor gives more weight to maintenance mode and decommission tasks over normal replication tasks.
 
However, if the configured value exceeds 10 (OUTOFSERVICE_FACTOR_MAX) it is reset back to 2 (OUTOFSERVICE_FACTOR_DEFAULT). This is totally unexpected. We should set it to OUTOFSERVICE_FACTOR_MAX in this case.
 

https://github.com/apache/ozone/blob/debc8abf484fbeae0331b0df9668ab997d8c8e8f/hadoop-hdds/container-service/src/main/java/org/apache/hadoop/ozone/container/replication/ReplicationServer.java#L284



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