swamirishi commented on PR #9132: URL: https://github.com/apache/ozone/pull/9132#issuecomment-3401110461
> > Will this cause compatbility problems if two OM in the same cluster are running different version, which could happen in rolling upgrade scenario. But we don't support rolling upgrade so this is a non-issue. > > Yep it can which is one of the reason's I remember I didn't want to change the format here cc @swamirishi Compatibility was already broken with the new implementation. The older implementation tarball didn't have inode ids for filenames. The hardlink file format also changed so we wouldn't be able to support rolling upgrade for this change. The only way we can support rolling upgrades would be to have the follower om still hit the old endpoint while the upgrade is in progress. -- 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]
