Ethan Rose created HDDS-15549:
---------------------------------
Summary: Recon's INITIAL_VERSION should not have an upgrade action
Key: HDDS-15549
URL: https://issues.apache.org/jira/browse/HDDS-15549
Project: Apache Ozone
Issue Type: Improvement
Reporter: Ethan Rose
Assignee: Ethan Rose
The standard in the upgrade framework is that INITIAL_VERSION serializes to 0
and represents the state before any upgrade framework was introduced, meaning
no version is found on disk. -1 is the in-memory serialized value representing
an unknown/future version in the ComponentVersion framework.
* Recon was using -1 as the in-memory placeholder to represent no version on
disk, and then INITIAL_VERSION = 0 as the first version to introduce the
upgrade framework. The creates a conflict with the standard versioning framework
* Recon had an upgrade action tied to INITIAL_VERSION, which ran because
initialization moved from version -1 to 0.
After HDDS-15374 switches Recon to the new versioning framework, Recon's
initialization code now reads no version being present as the initial 0
version. The upgrade action tied to version 0 will not run. To fix this, we can
merge version 0's upgrade action into version 1's upgrade action, so it will
still run if upgrading to this version from an old version before the
versioning framework. Note that the actions will be idempotent after HDDS-15488.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
