[
https://issues.apache.org/jira/browse/HDDS-15071?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18125263#comment-18125263
]
Wei-Chiu Chuang commented on HDDS-15071:
----------------------------------------
New optional SCM configuration hdds.scm.replication.reconstruction.global.limit
(default 0, disabled) caps cluster-wide in-flight EC reconstruction; when the
limit is reached, additional reconstruction is deferred until slots free up,
while decommission 1-1 replication continues. Default behavior is unchanged.
(PR: https://github.com/apache/ozone/pull/11054)
> [SCM] Add configuration and global reconstruction limit
> -------------------------------------------------------
>
> Key: HDDS-15071
> URL: https://issues.apache.org/jira/browse/HDDS-15071
> Project: Apache Ozone
> Issue Type: Task
> Reporter: Wei-Chiu Chuang
> Assignee: Wei-Chiu Chuang
> Priority: Major
> Labels: pull-request-available
> Fix For: 2.3.0
>
>
> Introduce the foundational configuration properties in
> ReplicationManagerConfiguration:
> * hdds.scm.replication.decommission.ec.reconstruction.enabled
> * hdds.scm.replication.decommission.ec.reconstruction.load.factor (default
> 0.9)
> * hdds.scm.replication.reconstruction.global.limit
> Implement an atomic counter in ReplicationManager to track active
> ReconstructECContainersCommand tasks cluster-wide. Update
> UnhealthyReplicationProcessor
> to check this global limit before dequeuing containers for reconstruction,
> ensuring aggregate bisectional bandwidth is protected.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
