bharatviswa504 commented on pull request #2730: URL: https://github.com/apache/ozone/pull/2730#issuecomment-954134491
> I'm adding an upgrade case for wider discussion: > > Assume, User OM has upgraded to OM_1.2.0 with `ozone.default.bucket.layout=OBS`. Now, OM will set default bucket layout to OBS if a client creates a new bucket without specifying bucket layout argument. > > **case-1)** step-1) An `old_client_1.1.0` creates a new bucket ` BUCKET_01` in OM_1.2.0 and the bucket will be created successfully with default bucket layout OBS. > > step-2) Now, new_client_1.2.0 performs o3fs/ofs operation on this new `BUCKET_01` then it will throw validation error. > > During upgrade there could be chances of both old_client_1.1.0 and new_client_1.2.0 co-exists, should we change the default value to `ozone.default.bucket.layout=LEGACY` ? With this the o3fs/ofs client will be happy and avoids validation errors. > > This is the reason(`ozone.default.bucket.layout=OBS`) for many test failures in our CI. > > @bharatviswa504, @mukul1987 welcome thoughts, thanks! I have few questions. 1. Can old client talk to FSO buckets? With this the o3fs/ofs client will be happy and avoids validation errors. We are doing validation only in new client, not understood still how it can make old clients happy? (Because during upgrade based on the enable flag, we will change all the bucket types to OBS/LEGACY right?) -- 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]
