The Aerospike Knowledge Base has moved to https://support.aerospike.com. Content on https://discuss.aerospike.com is being migrated to either https://support.aerospike.com or https://docs.aerospike.com. Maintenance on articles stored in this repository ceased on December 31st 2022 and this article may be stale. If you have any questions, please do not hesitate to raise a case via https://support.aerospike.com.
Aerospike with Primary Index on Disk fails to start with “missing or invalid mount point”
Problem Description
When configuring the All-Flash feature of Aerospike, the following message is displayed in the aerospike.log. The node does not start.
Aug 21 2019 08:34:59 GMT: FAILED ASSERTION (config): (cfg_ee.c:156) {test} missing or invalid mount point
Explanation
This message explains that a crucial check on the mountpoints specified in the config file has failed. In this situation, Aerospike cannot start. The reason for the check failing is shown in the WARNING line above the failed assertion. For example:
Aug 21 2019 08:34:59 GMT: WARNING (misc): (xmem_flash.c:156) index device size limit 5153960755200 higher than total file system size 5151444172800
Aug 21 2019 08:34:59 GMT: FAILED ASSERTION (config): (cfg_ee.c:156) {test} missing or invalid mount point
Solution
In the above case, the reason for failure was incorrect device size limit specification in the namespace configuration. The full size of the file system limits on all configured filesystems for the Index on Disk is smaller than the size limit in the config file. To correct this, the mounts-size-limit must be changed in the aerospike.conf file.
Other misconfiguration issues will display other indicative errors in the WARNING about the FAILED ASSERTION.
Notes
Take into account that the filesystem itself will have an overhead. Therefore, mounts-size-limit must be slightly lower than the filesystem size to accommodate for this.
Keywords
MOUNTS-SIZE-LIMIT ALL-FLASH INDEX DISK MISSING INVALID MOUNT POINT
Timestamp
September 2019