Estimated time to read: 2 minutes
Regular upgrades are strongly recommended to ensure your EraSearch deployment gets the latest bug fixes, performance enhancements, and new features. If you have any questions or concerns about upgrading, don't hesitate to reach out.
Upgrading to v1.22+ from v1.21 or earlier¶
In EraSearch v1.22.0, the Storage Service has a new 'mutable object' API for storing non-time-series objects. Due to this change, storage of internal metadata (for example, RBAC state) needs to be duplicated prior to upgrading.
This upgrade procedure is non-destructive, and only duplicates data from the old storage format (prior to the introduction of the 'mutable object' API) to the new location. If necessary, you can roll back the upgrade without consequence.
To upgrade to EraSearch v1.22 or later from v1.21 or earlier releases, do the following:
Upgrade to the v1.21.3 maintenance release. This release includes a pre-upgrade hook that you run to prepare the database for the v1.22+ data layout.
Once upgraded to v1.21.3, issue the following command using the
If the hook is successful, it will print out the message:
RELEASE_NAMEis the name of the Helm release used during the initial installation.
NAMESPACEis the name of the Kubernetes namespace where the EraSearch deployment resides.
Update the Helm values file (
values-eradb.yaml) to include a new
ALEXANDRIAD_STARTING_EPOCHenvironment variable for the Coordinator Service (denoted by the top-level
The value of this environment variable should be set to the string
"2"prior to upgrading.
Upgrade the database using the Helm
The upgrade command returns this output along with other deployment details:
For more information on the latest EraSearch releases, be sure to check out the changelog.