Quote taken: "When a record hits its expiration time the Namespace Supervisor will expire it, meaning it is removed from the cluster. An update or a touch from a client will reset the expiration time as if it were a new write. Reads will not affect expiration time. The namespace supervisor (NSUP) thread manages both evictions and expirations.
NSUP does not run all the time, instead it runs periodically. The time interval at which NSUP wakes up is the nsup-period"
Say a data expires, but NSUP hasn’t had the time to remove the data before the client issues an atomic increment to the data, and sets a special TTL value of -2 for not refreshing TTL. Will an atomic increment on the expired data refresh the object’s TTL and set the incremented value to 1?