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.

Sign up for GitHub

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

Jump to bottom

Region may not be removed in hot peer cache after merging #8698

Open
rleungx opened this issue Oct 14, 2024 · 0 comments · May be fixed by #8702
Open

Region may not be removed in hot peer cache after merging #8698

rleungx opened this issue Oct 14, 2024 · 0 comments · May be fixed by #8702
Labels
affects-5.4 affects-6.1 affects-6.5 affects-7.1 affects-7.5 affects-8.1 severity/major type/bug The issue is confirmed as a bug.

Comments

@rleungx
Copy link
Member

rleungx commented Oct 14, 2024 •
edited
Loading

Bug Report

If the region is not completely cooled down and the merge happens, it might be left in the hot peer cache and never be cleaned up. The merged region will never send a heartbeat again, resulting in checkExpiredTask not working.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
affects-5.4 affects-6.1 affects-6.5 affects-7.1 affects-7.5 affects-8.1 severity/major type/bug The issue is confirmed as a bug.
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

statistics: add gc in hot peer cache lhy1024/pd
2 participants
@jebter @rleungx