I tried digging a lot into redis documentation to figure out if a feature like above exists in redis or not but wasn't able to find any.

Agreed that this can be accomplished by setting the expiry to a newer time using EXPIRE, it makes sense for a key to auto refresh its expiry based on its access pattern thereby making TTL refreshes more application dependent [i.e. its access pattern] rather than blindly setting expiry manually on keys that may or may not even be accessed later on

You folks being the design experts here, what are the implications of implementing a feature like above? Or better put, why a feature like this was not considered?

Comment From: kalthas

Any progress? Or a module is the last resort?

Comment From: imoonkin

+1, I have an idea. Refresh expiration time with a probability when keys are accessed, the hotkeys remain in Redis, and low-frequency keys will be evicted eventually.