Upgrade Guide

Before upgrading from one version to another, please check the guide below.

Upgrading to version 0.5

⚠️ GeoIP legacy is not supported anymore, please use GeoIP2 databases.

⚠️ This is the first release to include a database upgrade strategy and it requires special attention. Versions prior to 0.5 are not aware of database versioning and cannot act accordingly if they run on a newer database model.

Expected downtime: < 5 minutes

1. Read the CHANGELOG.md since some command line arguments were changed, especially for running the server: -D becoming daemon.
2. If using redis sentinel, take at least half of the sentinels down: you don't want an unexpected failover during the upgrade.
3. Install Mirrorbits 0.5 on all instances without restarting the service(s).
4. Backup your master Redis instance:
   1. Run redis-cli SAVE and wait for the operation to finish.
   2. Copy redis on-disk database (usually from /var/lib/redis/dump.rdb) in a safe place.
5. Stop all Mirrorbits instances from the cluster you're about to upgrade.
6. Optional but recommended: start only one instance and follow the logs until you see: Database upgrade successful
7. Start all remaining instances.

Note I: during the upgrade all Mirrorbits instances will be prevented from using the database and therefore will only return results from the Fallbacks. At the time of the upgrade, be sure that this list is up-to-date.

Note II: Stats will not be lost, they will be kept in memory during the upgrade.

Troubleshooting

If the upgrade failed just re-install Mirrorbits 0.4. It should work without having to restore the database.

In any case, please open an issue.