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
In each loop, it will looking 64 keys to expire. If we repeat the process above for more than 64 keys, we will prevent the loop from removing new expiry entries!
The text was updated successfully, but these errors were encountered:
Describe the bug
With a new DB:
Logging the keys from expire.cpp, ie:
The output will be:
After 5s, the logs will stop, as the key has been removed from the expiry storage. All good.
Now, run this:
After 5s, the logs keep outputting, ie the expiry entry is stuck.
No matter what we do after this, eg
The expiry entry is still stuck. It gets worse, looking at the logic in expire.cpp:
In each loop, it will looking 64 keys to expire. If we repeat the process above for more than 64 keys, we will prevent the loop from removing new expiry entries!
The text was updated successfully, but these errors were encountered: