[
https://issues.apache.org/jira/browse/HDDS-7204?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Siddhant Sangwan updated HDDS-7204:
-----------------------------------
Summary: EC: Schedule UnderReplicatedProcessor and OverReplicatedProcessor
threads in RM instead of StorageContainerManager (was: Schedule
UnderReplicatedProcessor and OverReplicatedProcessor threads in RM instead of
StorageContainerManager)
> EC: Schedule UnderReplicatedProcessor and OverReplicatedProcessor threads in
> RM instead of StorageContainerManager
> ------------------------------------------------------------------------------------------------------------------
>
> Key: HDDS-7204
> URL: https://issues.apache.org/jira/browse/HDDS-7204
> Project: Apache Ozone
> Issue Type: Sub-task
> Components: SCM
> Reporter: Siddhant Sangwan
> Assignee: Siddhant Sangwan
> Priority: Major
> Fix For: 1.3.0
>
>
> Currently, UnderReplicatedProcessor and OverReplicatedProcessor are scheduled
> as BackgroundSCMService threads in StorageContainerManager. These processors
> directly depend on RM and should be managed by RM. This Jira moves their
> initialisation to the ReplicationManager class.
> Under and Over Replicated processors don't check whether they should continue
> running when processing their queues. This is a potential bug - they won't
> get interrupted when looping through a very large number of containers. This
> is fixed by including a check for ReplicationManager#shouldRun() inside the
> loop.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
