You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, I'm a bit confused as I'm not even sure if this is a bug or something else.
We use Redis as a cache, which we add via the setEx command. However, recently, we have started to have some keys that return -1 with the TTL command. It doesn't happen often, but such events do occur. What could be causing this?
The decrBy command is called with the same keys. Can this somehow affect the expire field?
Node.js Version
20
Redis Server Version
7.2.3
Node Redis Version
4.7.0
Platform
alpine
Logs
No response
The text was updated successfully, but these errors were encountered:
Description
Hi, I'm a bit confused as I'm not even sure if this is a bug or something else.
We use Redis as a cache, which we add via the setEx command. However, recently, we have started to have some keys that return -1 with the TTL command. It doesn't happen often, but such events do occur. What could be causing this?
The decrBy command is called with the same keys. Can this somehow affect the expire field?
Node.js Version
20
Redis Server Version
7.2.3
Node Redis Version
4.7.0
Platform
alpine
Logs
No response
The text was updated successfully, but these errors were encountered: