I have two aerospike clusters -
- Older cluster with the servers having the following combinations - storing data in disk + i2.2xlarge instances + Aerospike build vesion 126.96.36.199 - Newer cluster with the servers having the following combinations - storing data in memory + r3.4xlarge instances + Aerospike build version 188.8.131.52 + using partition-tree-sprigs
I wanted to compare the server side latencies and timeouts on them. I enabled the asgraphite daemon which comes in-built with Aerospike, by the following commands - python /opt/aerospike/bin/asgraphite --start --prefix aerospike.stats -g -p
I cannot see the latency stats against the old cluster in the graphite console.
Also, I am confused, as to which latency stat should I consider. Following stats are available against the older cluster -
Metric Value observed batch_index_timeout 0 batch_timeout 0 err_tsvc_requests_timeout ~80K
The batch stats are showing 0, as expected, because we are not doing any batch queries. The new cluster being higher than 3.9 does not have the err_tsvc_requests_timeout metric.
Link to question on stackoverflow - https://stackoverflow.com/questions/45236853/how-do-i-compare-latency-and-timeouts-at-server-side-between-two-aerospike-clust