I am trying to get the ttl of an object using GetHeader. However it seems the expiration returned is different from the one I set. Here is the code: package main import ( "fmt" "github.com/aerospike/aerospike-client-go" ) func main() { policy := aerospike.NewClientPolicy() // We need to requ…

I have read in other threads issues with clock skew. Perhaps when you run the server in docker / vagrant - some times there can be significant clock skew and then this TTL situation could possibly mess up. there is another thread on how to ensure the clocks are not skewed. See HLC jump warning in …

Expiration value returned is invalid

Client Libraries Go Client

isingh August 24, 2017, 5:18am 14

Thanks!! That makes sense. Looking at the code its clear that clock skew can cause these issues.

Set new system time Comes Write/Read Error

Topic		Replies	Views
Need help with ttl of keys in aerospike Installation	3	2363	February 6, 2018
Rate limit in golang Go Client	13	3702	February 2, 2017
Redis Vs Aerospike	2	147	April 17, 2024
On TTL when updating the record with the java client Java Client	3	2638	May 30, 2017
Aerospike expired data	5	3109	July 11, 2017

Expiration value returned is invalid

Related topics