Solution: Can’t convert persistent memory after upgrade
After upgrading from an Aerospike version prior to Aerospike 3.11 to a later version the following message is displayed in the Aerospike log:
Aug 02 2019 06:04:39 GMT: WARNING (namespace): (namespace_ee.c:280) can't convert persistent memory version 7 to 9
This is expected behaviour. The memory scheme for the Aerospike index was changed at Aerospike 3.11 and a cold start is required after the upgrade as documented in the special upgrades documentation in the upgrading past Aerospike 3.11 section. These error messages are not a cause for concern.
Aerospike will cold start shortly after the messages are displayed. During the cold start the primary index will be rewritten in the new format and the node will start as normal. It is also an option to cold start the node when starting after the upgrade.
- Details on how to effect a cold start are discussed here
- Details on the implications of a cold start are discussed here
COLD START AEROSPIKE 3.11 PERSISTENT MEMORY CONVERT