Skip to main content
Loading

Downgrade from Aerospike Database 7.0

info

Downgrading from Database 7.0 forces a cold start.

Configuration changes​

  1. All persisted CDT map indexes (not secondary indexes on CDT) must be removed from the cluster by the application before any nodes are downgraded. This can be achieved by applying a Map set_type operation with the persistIndex Map policy set to false.

  2. Before you downgrade from Database 7.0, drop any secondary indexes on blob-type elements before downgrading from Database 7.x to pre-7.0 because secondary indexes on blob-type elements are supported only in Database 7.0 and later. If you do not drop the secondary indexes you may get the following warning:

  1. The write-block-size default in Database 7.0 is 8MB for in-memory storage. To keep the storage-backed data, you must use a write-block-size of 8M. If you restart the node empty, you can use any value.

  2. Clean up the data shared memory stripes (prefix: '0xad') because they will be ignored by the older server code and consume memory. The forced cold start fills memory the old way and you end up with both copies of the memory if you don't clean up first.

    ipcs | grep ^0xad | awk '{print $1}' | xargs -i ipcrm -M {}

  3. Before you downgrade from Database 7.0, verify that the number of bins does not exceed the pre-7.0 limit. There is no bin limit per namespace in Database 7.0, but earlier versions have the following bin limits:

    • 64 * 1024 - 1 at the namespace level.
    • 32 * 1024 - 1 at the per-record level.

  4. Before you downgrade from Database 7.0, verify that the number of sets does not exceed 1023. The limit for the number of sets increased from 1023 to 4095 in Database 7.0. To check the number of sets in a namespace use the asinfo command:

    asinfo -v sets/$namespace -l | wc -l

  5. The downgrading server configuration option is removed in Database 7.0. You cannot downgrade directly from Database 7.0 to a version prior to Database 5.4 when using XDR bin convergence. You must first downgrade to Database 5.5 or 5.4, and then downgrade to an earlier version. For more information, see downgrading.

  6. You can downgrade to any supported server version (currently Database 6.1 and later). To downgrade to older versions, first consult the specific downgrade instructions for your desired version. We encourage Enterprise customers to open a case with Aerospike support.