[
https://issues.apache.org/jira/browse/HDDS-15326?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Attila Doroszlai updated HDDS-15326:
------------------------------------
Fix Version/s: 2.2.0
Resolution: Fixed
Status: Resolved (was: Patch Available)
> 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
> Assignee: Chi-Hsuan Huang
> Priority: Major
> Labels: pull-request-available
> Fix For: 2.2.0
>
>
> 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: [email protected]
For additional commands, e-mail: [email protected]
