errose28 commented on PR #3983: URL: https://github.com/apache/ozone/pull/3983#issuecomment-1372892063
Hey @symious sorry for the late response here. > For this one, currenlty the pre-finalized state is kind of automatic operation when we restart the servers with new binary package. I was wondering if a command to trigger pre-finalize is a more controllable way. Pre-finalize is a state where there is an unfinalized version of the software running on top of disk state written by an older version. It is not a command given to the cluster. Finalization is the command that is given by the user to finalize the cluster. > If the pre-finalize state is manually triggered, we can first do rolling upgrade to new binary package, and before pre-finalize, it is still possible to have the cluster available (both for read and write, current implementation is only readable). Ozone does not support rolling upgrades. This is its own feature that will need to be designed. Ozone is readable and writeable while pre-finalized. It will temporarily be read-only while being finalization completes, but we are working on removing this restriction for the next release. Some resources with more information: - https://ozone.apache.org/docs/1.3.0/feature/nonrolling-upgrade.html - https://www.apachecon.com/acna2022/slides/01_Rose_Inside_Ozone_Upgrade.pdf -- 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]
