New keys with TTL not deleted after expiration following update to include marker TTL

[ani-philips]

Observed behavior

I encountered an issue with the key-value store involving marker TTL functionality. Initially, I created the key-value store without setting a marker TTL. Later, I edited and updated the store to include a marker TTL and then added a new key with its own TTL. However, I've observed that the entity is not automatically deleted once its TTL expires.

Expected behavior

Upon editing the key-value store to include a marker TTL, any subsequently added key with its own TTL should be automatically deleted once the TTL expires.

Is this the behavior that is expected?

Server and client version

Server version: 2.11.3
Client version: 0.2.3

Host environment

Windows and Kubernetes

Steps to reproduce

nats kv add testkv
nats kv edit testkv --marker-ttl=30s
nats kv create testkv key value --ttl=20s
#Sleep
sleep 25s
nats kv get testkv key
#expectation is to not find the key. But the key is found

[ripienaar]

Yes, I can reproduce this, after first having no TTL and then edited to have a 30s one messages are not expiring:

[rip@s1-lon]% nats s get KV_TTL 1
Item: KV_TTL#1 received 2025-05-23 09:01:56.062067 +0000 UTC (39.64s) on Subject $KV.TTL.test

Headers:
  Nats-TTL: 10s
  Nats-Expected-Last-Subject-Sequence: 0

value

Note the message above is 40s old

% bin/nats s info KV_TTL --json
...
  "allow_msg_ttl": true,
  "subject_delete_marker_ttl": 30000000000,
...

[neilalexander]

Thanks for the report, the fix will merge shortly and will be included in 2.11.5.