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: Rebalancing should take region topology into consideration #35524

Closed
awoods187 opened this issue Mar 7, 2019 · 1 comment
Closed

storage: Rebalancing should take region topology into consideration #35524

awoods187 opened this issue Mar 7, 2019 · 1 comment
Labels
A-kv-distribution Relating to rebalancing and leasing. C-enhancement Solution expected to add code/behavior + preserve backward-compat (pg compat issues are exception) X-duplicate Closed as a duplicate of another issue. X-stale

Comments

@awoods187
Copy link
Contributor

Is your feature request related to a problem? Please describe.
Rebalancing should take region topology into consideration. If we can safely rebalance to another node in the same region we should do this rather than traveling across to another region.

This will reduce the cost of rebalancing and speed it up to get to a recovered state faster.
@awoods187 awoods187 added C-enhancement Solution expected to add code/behavior + preserve backward-compat (pg compat issues are exception) A-kv-distribution Relating to rebalancing and leasing. labels Mar 7, 2019
@awoods187 awoods187 changed the title Rebalancing should take region topology into consideration storage: Rebalancing should take region topology into consideration Mar 13, 2019
@lunevalex
Copy link
Collaborator

Dupe of #42491

@lunevalex lunevalex added the X-duplicate Closed as a duplicate of another issue. label Apr 23, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
A-kv-distribution Relating to rebalancing and leasing. C-enhancement Solution expected to add code/behavior + preserve backward-compat (pg compat issues are exception) X-duplicate Closed as a duplicate of another issue. X-stale
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@awoods187 @lunevalex