Downgrades of Riak are tested and supported for two feature release versions, with the general procedure being similar to that of a rolling upgrade.
Depending on the versions involved in the downgrade, there are additional steps to be performed before, during, and after the upgrade on on each node. These steps are related to changes or new features that are not present in the downgraded version.
We test and support downgrading for two feature release versions. However, two feature release versions below KV 2.1.3 is 1.4.12. KV 1.4.12 was declared End Of Life (EOL) and no longer supported in November 2015. Please be aware of that if you choose to downgrade.
For every node in your Riak cluster:
- Stop Riak KV.
- Back up Riak’s
- Downgrade Riak KV.
- Start Riak KV.
- Finalize the process.
The below instructions describe the procedures required for a single feature release version downgrade (for instance from 2.1.3 to 2.0.7). In a downgrade between two feature release versions (say 2.1.3 to 1.4.12), the steps for the in-between version must also be performed. For example, a downgrade from 2.1.3 to 1.4.12 requires that the downgrade steps for both 2.1.3 and 2.0.7 are performed.
- Riak control should be disabled throughout the rolling downgrade process
- Configuration Files must be replaced with those of the version being downgraded to
While the cluster contains mixed version members, if you have not set the cluster to use the legacy AAE tree format, you will see the
bad_version error emitted to the log any time nodes with differing versions attempt to exchange AAE data (including AAE fullsync).
This is benign and similar to the
already_locked errors which can be seen during normal AAE operation. These events will stop once the downgrade is complete.
Stop Riak KV, back up, & downgrade
1. Stop Riak KV:
2. Back up your Riak KV /etc and /data directories:
sudo tar -czf riak_backup.tar.gz /var/lib/riak /etc/riak
3. Downgrade Riak KV:
sudo rpm -Uvh »riak_package_name«.rpm
sudo dpkg -i »riak_package_name«.deb
Start the node & finalize process.
4. Start Riak KV:
5. Verify that transfers have completed:
Monitor the reindex of the data
After your downgrade, you may want to monitor the build and exchange progress of the AAE trees using the
riak-admin aae-status and
riak-admin search aae-status commands.
The All column shows how long it has been since a partition exchanged with all of its sibling replicas. Consult the
riak-admin aae-status documentation for more information about the AAE status output.
Once both riak-admin aae-status and riak-admin search aae-status show values in the All column, the node will have successfully rebuilt all of the indexed data.