Documentation of namespace related metrics


#1

Hi,

asinfo -v "namespace/users" prints metrics which unfortunately are not documented in http://www.aerospike.com/docs/reference/metrics

For instance:

Where could I find description of these stats?


#2

Hi,

Thanks for reaching out.

  • cache-read-pct has been missing from the metrics reference manual but should show up later today. It has been renamed to cache_read_pct as of version 3.9.
  • I am not sure what writecache is, what are you referring to?
  • max-write-cache is a configuration parameter and is documented on the configuration reference manual, on this page.

We have a convention that version 3.9 is now much more consistent with, to have configuration variable with ‘-’ delimiters and statistics/metrics with ‘_’ delimiters in their names.


#3

Hi,

Thank you for fast reply.

In our env writecache=1073741824

Aerospike 3.8.3

$ asinfo -v "namespace/users" type=device;objects=466055990;sub-objects=0;master-objects=211390266;master-sub-objects=0;prole-objects=254665722;prole-sub-objects=0;expired-objects=0;evicted-objects=0;set-deleted-objects=0;nsup-cycle-duration=111;nsup-cycle-sleep-pct=0;used-bytes-memory=29827583360;data-used-bytes-memory=0;index-used-bytes-memory=29827583360;sindex-used-bytes-memory=0;free-pct-memory=62;max-void-time=211485115;non-expirable-objects=0;current-time=206301115;stop-writes=false;hwm-breached=false;available-bin-names=32760;migrate-tx-partitions-imbalance=0;migrate-tx-instance-count=0;migrate-rx-instance-count=0;migrate-tx-partitions-active=0;migrate-rx-partitions-active=0;migrate-tx-partitions-initial=36;migrate-tx-partitions-remaining=0;migrate-rx-partitions-initial=36;migrate-rx-partitions-remaining=0;migrate-records-skipped=357979;migrate-records-transmitted=12790858;migrate-record-retransmits=0;migrate-record-receives=32999;used-bytes-disk=227987645184;free-pct-disk=94;available_pct=91;cache-read-pct=72;memory-size=80530636800;high-water-disk-pct=50;high-water-memory-pct=60;evict-tenths-pct=5;evict-hist-buckets=10000;stop-writes-pct=90;cold-start-evict-ttl=4294967295;repl-factor=2;default-ttl=5184000;max-ttl=315360000;conflict-resolution-policy=generation;single-bin=false;ldt-enabled=false;ldt-page-size=8192;enable-xdr=false;sets-enable-xdr=true;ns-forward-xdr-writes=false;allow-nonxdr-writes=true;allow-xdr-writes=true;disallow-null-setname=false;total-bytes-memory=80530636800;read-consistency-level-override=off;write-commit-level-override=off;migrate-order=5;migrate-sleep=1;total-bytes-disk=3997559685120;defrag-lwm-pct=50;defrag-queue-min=0;defrag-sleep=1000;defrag-startup-minimum=10;flush-max-ms=1000;fsync-max-sec=0;max-write-cache=1073741824;min-avail-pct=5;post-write-queue=256;data-in-memory=false;dev=/dev/sdb1;dev=/dev/sdc1;dev=/dev/sdd1;dev=/dev/sde1;dev=/dev/sdf1;dev=/dev/sdg1;dev=/dev/sdh1;dev=/dev/sdi1;dev=/dev/sdj1;dev=/dev/sdk1;filesize=17179869184;writethreads=1;writecache=1073741824;obj-size-hist-max=100


#4

Ah, yes, I just noticed too on my install… it is the same as write-max-cache, so not needed.