JacksonYao287 commented on PR #3455: URL: https://github.com/apache/ozone/pull/3455#issuecomment-1197988971
> I think there is a new RM being added as part of EC. Please refer https://issues.apache.org/jira/browse/HDDS-6589. > > I think the handling of over and under replicated containers is different in EC. Since move relies on the RM handling of over-replicated containers, logic should be affected for move in case of EC containers. Please correct me if I am wrong. we don`t want to implement EC over and under-replicated handling logic in RM directly since it is too complex. so we convert old RM to legacyReplicationManager and create a new RM. then Ratis container will be forwarded by the newly created one to legacyReplicationManager, so that we can keep the current Ratis container process flow. for EC container, it will be processed in the newly created RM by the newly implmented over and under replicated handlers. so , in fact , we have two separate process flow for Ratis and EC container. also, any call to replicationManager#move will be forwarded to legacyReplicationManager#Move, so the current move api will not be affected. move api should be a independent functionality which is not aware of the container type, and i have a jira(https://issues.apache.org/jira/browse/HDDS-6572) to split move scheduler from legacy RM. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
