wget -O aerospike.tgz 'http://aerospike.com/download/server/latest/artifact/ubuntu12' tar -xvf aerospike.tgz cd aerospike-server-community-*-ubuntu12* sudo ./asinstall # will install the .rpm packages sudo service aerospike start
Write Key Value
ns the namespace for the record being written.
The set is the set for the record being written.
The key is the key for the record being written. It can be either an > integer or string.
The record is a JSON object representing the record to be written. The JSON object’s keys are the bin names and the value are bin values.
Reading Key Value
Reading All Values
- Enter aql command in terminal
- Enter bellow query
select * from
Start, Stop and Restart aerospike service
sudo service aerospike start sudo service aerospike stop sudo service aerospike restart
after restart service, all stored data will be cleaned.
Reserved TCP Ports
|Service||3000||Application, Tools, and Remote XDR use the Service port for database operations and cluster state.|
|Fabric||3001||Intra-cluster communication port. Replica writes, migrations, and other node-to-node communications use the Fabric port.|
|Mesh Heartbeat||3002||Heartbeat protocol ports are used to form and maintain the cluster. (Only one heartbeat port may be configured.)|
|Multicast Heartbeat||9918||Heartbeat protocol ports are used to form and maintain the cluster. (Only one heartbeat port may be configured.)|
|Info||3003||Telnet port that implements a plain text protocol for administrators to issue info commands. For more information, see asinfo documentation.|
|XDR Service1||3004||(Optional) Port to query health state of the Cross Datacenter Replication (XDR) client.|
- Ensure that all Application and XDR nodes can communicate to the service port on all Aerospike nodes. Also ensure that each node can communicate over the configured heartbeat and fabric ports. ↩