I am running load testing using Aerospike 3.7.3, community edition and have a recurring issue where some of the histograms will randomly stop populating, most important of all, write_master. Nothing I can do short of restarting the server will reactivate it but that generates migrations (which affects my numbers) and it will eventually stop logging. Running hist-track-stop/start doesn’t help and neither does changing the logging parameters nor turning microbenchmarks on/off.
I can verify that traffic is still passing through the system and if I turn on microbenchmarks or storage-benchmarks I do get some stats, but none of the base histograms are working.
My only configuration for logging is “context any info” and there are no issues with permissions. This cluster is in AWS inside our VPC using a mesh of 5 nodes with SSD storage on the built in ephemeral drives. The traffic is, for this test, 100% writes.