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
Bot detected the issue body's language is not English, translate it automatically.
The reason for this problem is that the order cannot be guaranteed when applying binlog from the slave node, so flushdb may be executed before set, resulting in dirty data from the slave node, which has nothing to do with the cache. The solution is to check before and after flushdb.
Is this a regression?
Yes
Description
There was a problem when go integrated testing the idea, but the problem was not reproduced locally, it should be a problem caused by pika cache
集成测试的 CI 报了下面的问题,但是本地没有复现,猜测应该是 Pika 缓存导致的问题,非必现。先记录这个issue,今天继续排查原因
Please provide a link to a minimal reproduction of the bug
No response
Screenshots or videos
Please provide the version you discovered this bug in (check about page for version information)
No response
Anything else?
No response
The text was updated successfully, but these errors were encountered: