Upgrading to ArangoDB 2.2
Please note first that a database directory used with ArangoDB 2.2 cannot be used with earlier versions (e.g. ArangoDB 2.1) any more. Upgrading a database directory cannot be reverted. Therefore please make sure to create a full backup of your existing ArangoDB installation before performing an upgrade.
ArangoDB will perform a database version check at startup. When ArangoDB 2.2 encounters a database created with earlier versions of ArangoDB, it will refuse to start. This is intentional.
The output will then look like this:
To make ArangoDB 2.2 start with a database directory created with an earlier ArangoDB version, you may need to invoke the upgrade procedure once. This can be done by running ArangoDB from the command line and supplying the option:
where data
is ArangoDB’s main data directory.
Note: here the same database should be specified that is also specified when arangod is started regularly. Please do not run the --upgrade
command on each individual database subfolder (named ).
then running
unix> arangod mydatabasefolder --upgrade
will perform the upgrade for the whole ArangoDB instance, including all of its databases.
Starting with --upgrade
will run a database version check and perform any necessary migrations. As usual, you should create a backup of your database directory before performing the upgrade.
The output should look like this:
Please check the output the --upgrade
run. It may produce errors, which need to be fixed before ArangoDB can be used properly. If no errors are present or they have been resolved, you can start ArangoDB 2.2 regularly.
Upgrading a cluster planned in the web interface
A cluster of ArangoDB instances has to be upgraded as well. This involves upgrading all ArangoDB instances in the cluster, as well as running the version check on the whole running cluster in the end.
First shut down your cluster using the graphical front end as usual.
Now open the cluster dash board in your browser by pointing it to the same dispatcher that you used to plan and launch the cluster in the graphical front end. In addition to the usual buttons “Relaunch”, “Edit cluster plan” and “Delete cluster plan” you will see another button marked “Upgrade and relaunch cluster”.
Hit this button, your cluster will be upgraded and launched and all is done for you behind the scenes. If all goes well, you will see the usual cluster dash board after a few seconds. If there is an error, you have to inspect the log files of your cluster ArangoDB instances. Please let us know if you run into problems.
There is an alternative way using the shell. Instead of steps 3. and 4. above you can launch arangosh
, point it to the dispatcher that you have used to plan and launch the cluster using the option --server.endpoint
, and execute
This upgrades the cluster and launches it, exactly as with the button above in the graphical front end. You have to replace with a user name and ""
with a password that is valid for authentication with the cluster.