It seems under some circumstances single key can be present in cache twice, or at least have a duplicate in expiration queue.
It happens like this:
Some keys get added to cache, some get updated to extend their TTL.
I dump cache content periodically and see item will be valid, for example, for 10 more seconds.
After, for example, 5 seconds OnEviction hook fires for that element.
I prolong key for 10 more seconds immediately.
Apparently some "lost" key gets prolonged and early OnEviction happens again even tho Item in cache is supposed to expire later.
It feels like in some place which works with expiration queue is not synchronized with storage update and/or duplicate item gets into expiration queue.
I'm using v3.1.1. Unfortunately, that's as much details I can provide, I triggered this issue only in prod environment and didn't managed to reproduce it locally.
It seems under some circumstances single key can be present in cache twice, or at least have a duplicate in expiration queue.
It happens like this:
It feels like in some place which works with expiration queue is not synchronized with storage update and/or duplicate item gets into expiration queue.
I'm using v3.1.1. Unfortunately, that's as much details I can provide, I triggered this issue only in prod environment and didn't managed to reproduce it locally.