A logging interface is provided to handle log messages generated by the client. Most log messages are generated from background cluster tend thread(s) created for each client instance. Messages include node additions/removal and any errors when retrieving node status, peers, partition maps and racks. This information is critical to debug transaction failures resulting from cluster tend errors.
Configure and connect the Aerospike C client to the Aerospike cluster.
📄️ Error Handling
Manage errors using the Aerospike C client and the Aerospike database.
📄️ Async API
Aerospike C Client asynchronous API tutorial.
📄️ Shared Memory
Enable shared memory for client cluster tending.
🗃️ Best Practices
Use the Aerospike C client library benchmark with the Aerospike database.
📄️ Incompatible API Changes
Compatibility issues with the Aerospike C client.