sumitagrawl opened a new pull request, #5543: URL: https://github.com/apache/ozone/pull/5543
## What changes were proposed in this pull request? Replication under timeout case can cause to replicate container to same target but from different source. So, when import is executed at DN for container during replication, there is no check and container exist verified only at end while adding to containerSet, this can have adverse impact as: - In multi-volume case, Volume chosen for second import is different volume, then import will be success but add to container set will be ignored/failed. This impact un-necessary disk occupy. - When container import in progress parallel to same volume, "delete, untar container file, copy to destination" operation in certain sequence to same volume location can cause missing chunk or corruption. so, during import, it does below check before operation starts, - check if container is already imported to containerSet - check if already container import is in-progress or not ## What is the link to the Apache JIRA https://issues.apache.org/jira/browse/HDDS-9588 ## How was this patch tested? 1. UT case for checking parallel import 2. Existing integration test -- 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]
