Downgrade from Database 7.2

This page provides important information about performing a downgrade from Database 7.2.

Overview

If active-rack has been enabled in Database 7.2, it must be disabled on all nodes before downgrading.

Caution

If you are using SC mode and have not updated the roster with the active-rack removed, migrations will fail because roster parsing differs. As you downgrade through a rolling restart, the cluster node will throw the following warnings:

WARNING (roster): (roster_ee.c:151) illegal node id 0
WARNING (roster): (roster_ee.c:237) {test} invalid node list M100|bb...01|

Disable active rack for Available and Partition-tolerant (AP) mode

1. Use asadm to disable active-rack in AP namespaces:

   Admin> enable
   Admin+> manage config namespace ns-name param active-rack to 0
   ~Set Namespace Param active-rack to 0~
            Node|Response
   10.1.0.1:3000|ok
   10.1.0.2:3000|ok
   10.1.0.3:3000|ok
   Number of rows: 3

2. Recluster for your active-rack to take effect.

   Admin+> manage recluster
   Successfully started recluster

3. Remove the active-rack line from aerospike.conf on all nodes before downgrading from Database 7.2.

Disable active rack for Strong Consistency (SC) mode

1. Use asadm to disable active-rack in SC namespaces:

   Admin> enable
   Admin+> manage config namespace ns-name param active-rack to 0
   ~Set Namespace Param active-rack to 0~
            Node|Response
   10.1.0.1:3000|ok
   10.1.0.2:3000|ok
   10.1.0.3:3000|ok
   Number of rows: 3

2. Recluster for your active-rack to take effect.

   Admin+> manage recluster
   Successfully started recluster

3. Modify the pending roster changes.

   Admin+> manage roster stage observed ns ns-name
   Pending roster now contains observed nodes.

4. Recluster again for changes to take effect.

   Admin+> manage recluster
   Successfully started recluster

5. Remove the active-rack line from aerospike.conf on all nodes before downgrading from Database 7.2.