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

Evicting slow stores may trigger redundant scheduling #8895

Open
mayjiang0203 opened this issue Dec 11, 2024 · 2 comments · May be fixed by #8912
Open

Evicting slow stores may trigger redundant scheduling #8895

mayjiang0203 opened this issue Dec 11, 2024 · 2 comments · May be fixed by #8912
Labels
affects-7.5 This bug affects the 7.5.x(LTS) versions. report/customer Customers have encountered this bug. type/enhancement The issue or PR belongs to an enhancement.

Comments

@mayjiang0203
Copy link

Enhancement Task

There are many redundant scheduling after evict-slow-store has been triaggered.

Image

Image

Image

@mayjiang0203 mayjiang0203 added the type/enhancement The issue or PR belongs to an enhancement. label Dec 11, 2024
@lhy1024
Copy link
Contributor

lhy1024 commented Dec 11, 2024

Because we select target for evict leader from follower randomly, the cluster is not even and need to balance leader again.
Maybe we should sort store according to the num of leader rather than random.
But I am not sure whether it will affect performance.

target := candidates.RandomPick()

@lhy1024 lhy1024 linked a pull request Dec 12, 2024 that will close this issue
@seiya-annie
Copy link

/report customer

@ti-chi-bot ti-chi-bot bot added report/customer Customers have encountered this bug. affects-7.5 This bug affects the 7.5.x(LTS) versions. labels Dec 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
affects-7.5 This bug affects the 7.5.x(LTS) versions. report/customer Customers have encountered this bug. type/enhancement The issue or PR belongs to an enhancement.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants