Gargi-jais11 commented on PR #10022: URL: https://github.com/apache/ozone/pull/10022#issuecomment-4242006090
> While balancer moves the QC container, If we don't do the bcsId check it can increase the containers that have lower bcsId by the balancer selecting it and delete not processing in the system. @sadanand48 What I know is that **BCSID** increases when new block commits go through the container pipeline (Ratis log index on PutBlock). Balancers relocate bytes and metadata; they should preserve BCSID. Neither Disk Balancer nor Container Balancer is meant to raise BCSID when a container is moved. They copy the existing replica , so the moved replica should keep the same BCSID as the source and stay aligned with SCM’s container sequence id—same as any other replication or import of a closed/quasi-closed replica. So I don't think even after moving quasi closed containers there will be any issue related to processing the deletion of quasi clsoed containers. It will be deleted correctly by RM with new updated location, if I am not wrong here in my understanding. I think we allow quasi closed containers to be moved without any config unless we want to play safe. Please share you opinions. cc: @ChenSammi @errose28 @ashishkumar50 -- 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]
