Unexpected records evicted

Operations
1

Hi there,

I noticed that there were records evicted right after the node was added into a cluster.

Both free space of disk and memory are enough, how to understand the evicting here?

Apr 23 2020 14:40:29 GMT: INFO (nsup): (nsup.c:212) starting namespace supervisor threads
Apr 23 2020 14:40:31 GMT: INFO (nsup): (nsup.c:324) {event} got smd evict-void-time 325045682
Apr 23 2020 14:40:31 GMT: INFO (nsup): (nsup.c:525) {event} nsup-start: evict-threads 1 evict-ttl -303149 evict-void-time (0,325045682)
Apr 23 2020 14:40:31 GMT: INFO (nsup): (nsup.c:533) {event} now (325348831) > evict-void-time - using now
Apr 23 2020 14:40:31 GMT: INFO (nsup): (nsup.c:836) {event} nsup-done: non-expirable 0 expired (0,0) evicted (12,12) evict-ttl -303149 total-ms 12
Apr 23 2020 14:41:29 GMT: INFO (nsup): (nsup.c:427) {event} nsup-start: expire-threads 1
Apr 23 2020 14:41:29 GMT: INFO (nsup): (nsup.c:836) {event} nsup-done: non-expirable 0 expired (1450,1450) evicted (12,0) evict-ttl -303149 total-ms 158
Apr 23 2020 14:42:29 GMT: INFO (nsup): (nsup.c:427) {event} nsup-start: expire-threads 1

I’m running Aerospike Community Edition build 4.9.0.5

2

As of version 4.5.1 the expiration and eviction mechanism was changed. Instead of going after master records only on each node and generating delete transactions to propagate to replicas, nodes would go after both master and replicas but will exchange timestamps (through SMD) so that all nodes expire ‘in sync’ and evict at the same ‘depth’.

3

Thank you for your reply. I found the detailed faq.

4

This topic was automatically closed 6 days after the last reply. New replies are no longer allowed.