Linking to a related question you just asked about deploying on multiple AZs, in which we recommended the correct way of using Aerospike on EC2: building a cluster in a single AZ - better yet a single placement group within it - and using either an application-level synchronization with something like Kafka, or using our Enterprise Edition feature, XDR (cross-datacenter replication) to another AZ or region.
Related topics
| Topic | Replies | Views | Activity | |
|---|---|---|---|---|
| Observing steady increase timeouts from aerospike server | 0 | 1744 | March 10, 2016 | |
| Error in delay connects after system ready message | 11 | 3889 | October 13, 2015 | |
| Node crash in AWS using the Aerospike AMI | 9 | 5110 | September 23, 2019 | |
| Hits AEROSPIKE_ERR_TIMEOUT more often than I should | 12 | 4021 | May 14, 2015 | |
| One node showing inexplicably high read latency/CPU load | 10 | 5848 | October 28, 2015 |