F64116045 commented on PR #11199: URL: https://github.com/apache/ozone/pull/11199#issuecomment-5586287857
> I know it says mentioned debouncing in the Jira, but that was clearly generated by an AI and I am not sure it makes sense? Thanks for questioning. I went back and checked the cases it was meant to cover, including replicas that have not produced a checksum yet, Datanode reports arriving at different times, and checksum changes during scanning or reconciliation. We already skip the comparison until every replica has reported a non-zero checksum. Normal block deletion keeps the checksum unchanged. Also if a different checksum arrives after that container has already been checked, the mismatch will be detected in the next scan So I think you’re right that waiting for a second scan does not add any useful confirmation here. I’ll remove the debounce, and thanks again for pointing this out. -- 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]
