This section describes how to upgrade a Neo4j HA cluster.
Upgrading a Neo4j HA cluster to Neo4j 3.3.1 requires following a specific process in order to ensure that the cluster remains consistent, and that all cluster instances are able to join and participate in the cluster following their upgrade.
Please note that Neo4j 3.3.1 does not support rolling upgrades.
dbms.mode=SINGLEin neo4j.conf to disable HA in the configuration.
dbms.mode=HAin neo4j.conf to re-enable HA in the configuration.
Make a full backup of the Neo4j database.
Please note that backups taken before the upgrade are no longer valid for update via the incremental online backup. Therefore, it is important to perform a full backup, using an empty target directory, at this point.
On each slave:
dbms.active_databasein neo4j.conf to the name of the database.
At this point it is an alternative to manually copy database directory from the master to the slaves. Doing so will avoid the need to sync from the master when starting. This can save considerable time when upgrading large databases.
Once a slave has joined the cluster, it will sync the database from the master instance.