[
https://issues.apache.org/jira/browse/HDDS-6895?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17558235#comment-17558235
]
Stephen O'Donnell commented on HDDS-6895:
-----------------------------------------
At the moment I am thinking to queue them, but I am not sure. They are not as
intensive as replication commands, but we also don't want to flood the DNs with
them either. Probably makes sense to handle them in a separate queue from under
replications.
> EC: ReplicationManager - Logic to process the under/over replicated queues
> and assign work to DNs
> -------------------------------------------------------------------------------------------------
>
> Key: HDDS-6895
> URL: https://issues.apache.org/jira/browse/HDDS-6895
> Project: Apache Ozone
> Issue Type: Sub-task
> Components: SCM
> Reporter: Stephen O'Donnell
> Assignee: Attila Doroszlai
> Priority: Major
>
> We need some sort of thread which picks work from the under / over replicated
> queue and assigns the work to DNs with capacity. The DNs will pick the work
> up on each heartbeat.
> This would use the class created in another Jira to create the command to fix
> the replication issue.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
