Skip to main content

Downgrade from Aerospike Database version 5.2 or newer

Downgrading from Aerospike Database version 5.2 or newer to a version previous to 5.2 (where XDR bin shipping has been used).

On a Aerospike Database version 5.2 or newer node, if the XDR DC namespace context configuration item config bin-policy has been set to anything other than 'all' (the default), bin metadata and/or bin tombstones may have been generated and stored within records. When migrating such records to nodes of a version previous to 5.2 during a downgrade, the older nodes will not be able to read these records.

Before downgrading, dynamically set bin-policy to 'all' and downgrading to 'true' on every node. When restarting a node with a version previous to 5.2, the drives must be wiped in order to remove unreadable records.

note

If downgrading from Aerospike Database version 5.4 or newer where the bin convergence feature has been enabled, convergence-related configurations must be switched off when setting bin-policy to 'all'.