Incorrect expiry

Couchbase Server
1

Hello,

The application is setting the TTL to 40 seconds, but when we check the expiry on the server side, we see that it’s set to less than 40 seconds. In some cases, the timestamp even appears to be in the past, i.e., earlier than the insertion time.

The CAS timestamp, however, is correct.

Here’s what we’ve checked so far:

  • NTP is functioning properly.
  • The time between the app and the Couchbase server is mostly in sync, with only a few milliseconds of difference.
  • The hwclock and date on the Couchbase server match the same time.
  • We’ve confirmed via tcpdump on the Couchbase server that the correct 40-second expiry value is being received.

Can some debug logging be enabled on Couchbase server side that will show what is added to 40 sec to arrive at the expiry timestamp?

Any other insights or suggestions would be greatly appreciated.

Thanks!

2

Hi - it appears you have a ticket open with support and they have information for you.