chungen0126 commented on PR #11685: URL: https://github.com/apache/ozone/pull/11685#issuecomment-6420321545
Hi @devmadhuu , thanks for catching this edge case! However, do we really need to handle this for backward compatibility? These records only exist on clusters upgraded from a release before ozone 2.0 with incomplete FSO multipart uploads. MultipartUploadCleanupService aborts any MPU older than `ozone.om.open.mpu.expire.threshold`. These uploads were initiated before the upgrade, they are gone within about 31 days after upgrade. Is it worth adding more code complexity just to avoid a monitoring inaccuracy during that window? -- 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]
