On 4/20/21 9:02 AM, Kota Uenishi wrote:
We're planning to upgrade our bare metal cluster to 1.1.0 and want to know any important notice. I think I've seen some argument that rolling upgrade isn't supported on the path from 1.0 to 1.1. Is it straightforward like just injecting configuration XMLs to the ozone-1.1.0/etc/hadoop directory and restarting all process at once? I hope so, but things can easily go wrong and I want to be prepared.
Thanks to HDDS-3855 and HDDS-4741 (and other smaller patches) we have upgrade test for each of the PR and master as part of the CI.
I just double checked and the results can be found in the acceptance-misc.zip artifact from any of the builds.
This test creates data with older version of Ozone (0.5.0 or 1.0.0), stops the cluster, and starts the actual version the same data directory.
So the answer is yes: the upgrade supposed to be as easy as replacing the ozone distribution (however making a backup from metadata dirs couldn't be a mistake anytime ;-) ).
The soon-to-be-merged upgrade framework provides additional feature: You can upgrade the jar files but keep the metadata compatible with the old version as long as you testing new release.
When you "finalize" this test period, the new features become available and new style of metadata also will be used and persisted (which makes it impossible to downgrade after this step).
Marton --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@ozone.apache.org For additional commands, e-mail: dev-h...@ozone.apache.org
