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

storage: make AdminScatter less best-effort #15049

Closed
danhhz opened this issue Apr 18, 2017 · 1 comment
Closed

storage: make AdminScatter less best-effort #15049

danhhz opened this issue Apr 18, 2017 · 1 comment
Assignees
@benesch
Milestone
1.1

Comments

@danhhz
Copy link
Contributor

danhhz commented Apr 18, 2017

RESTORE splits out all the new ranges and uses the leaseholders to distribute the data import work, so there's a big performance (and cluster stability) improvement when scatter works well. It's currently best-effort, so if the cluster is unbalanced when the RESTORE starts, then the replication queues will be doing work and the snapshots for scatter will be rejected.
@danhhz danhhz added this to the 1.1 milestone Apr 18, 2017
@danhhz danhhz mentioned this issue Apr 18, 2017
Merged
@danhhz
Copy link
Contributor Author

danhhz commented Jul 17, 2017

Closed in #16249

@danhhz danhhz closed this as completed Jul 17, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@benesch benesch

Labels
None yet
Projects
None yet
Milestone
1.1
Development

No branches or pull requests
2 participants
@danhhz @benesch