Install and deploy the Aerospike Java Client.
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.
The Aerospike client object can connect and periodically ping nodes for the current state of the cluster.
Java client usage
📄️ Error Handling
Aerospike java client error handling.
🗃️ Async API
📄️ First Program Guide
A guide to writing two Aerospike programs, which both operate on multiple records
📄️ Supported Data Types
The Aerospike database supports several data types including string, integer, blog, map, and lists using the Aerospike Java client
🗃️ Object Mapping
📄️ Best Practices
Follow these best practices when using the Aerospike Java client API.
Use the Aerospike Java client benchmarks tool to generate load on an Aerospike cluster and calculate performance metrics.
📄️ Incompatible API Changes
Compatibility issues with the Aerospike Java client.