by Hanson » Thu Jul 24, 2014 8:02 pm
I’m using Aerospike 3.3.8 In-Memory with disk Persistence.
I tried to insert a new record, and checked the persistence data file, but found the timestamp of it has not been changed after I have inserted that record for a long time.
Seems Aerospike will not flush changed data from memory into disk if the buffer is not full.
Shouldn’t also flush changed data from memory into disk per time interval? e.g.: either buffer is full or interval > 1 second since last flush.
The changed data can be persistent if I use “service aerospike restart” to restart the Aerospike, but lost if “kill -9 ”.