Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cache item maybe missed in hot peer cache #2468

Closed
lhy1024 opened this issue May 27, 2020 · 0 comments · Fixed by #2463
Closed

Cache item maybe missed in hot peer cache #2468

lhy1024 opened this issue May 27, 2020 · 0 comments · Fixed by #2463
Labels
component/scheduler Scheduler logic. type/bug The issue is confirmed as a bug.
Milestone

Comments

@lhy1024
Copy link
Contributor

lhy1024 commented May 27, 2020

If the region is balanced from a store to another store or the leader is transferred, the region and store info will be expired in hotPeerCache.

We statistic the flow by comparing the current time with the previous time, which will cause the existence of zero in the previous time after balance or transfer. In order to avoid sudden fluctuations, we chose to use the region info of other stores as the last time.

But tmpItem will be affected by the expired store. if there are store1, store2, and store3, and move peer to store4, the new replica cannot get cached from all unexpired stores.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
component/scheduler Scheduler logic. type/bug The issue is confirmed as a bug.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants