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	2389	February 6, 2018
AQL insert with TTL expires in the past AQL	2	4801	October 23, 2015
Rate limit in golang Go Client	13	3748	February 2, 2017
Expired records takes old values and update TTL Deletion deletion	12	2304	January 14, 2019
Redis Vs Aerospike	2	175	April 17, 2024

Expiration value returned is invalid

Related topics