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

Allocations to priority peers result in inbalances #1764

Open
hsanjuan opened this issue Sep 16, 2022 · 0 comments
Open

Allocations to priority peers result in inbalances #1764

hsanjuan opened this issue Sep 16, 2022 · 0 comments
Labels
exp/expert Having worked on the specific codebase is important kind/enhancement A net-new feature or improvement to an existing feature P1 High: Likely tackled by core team if no one steps up

Comments

@hsanjuan
Copy link
Collaborator

The allocator has a very naïve approach when priority peers are specified: they are just sorted and put in front of the list.

That creates some effects. I.e. if a priority peer is in the US region and put first in the list, then the next peer in the list (not priority), may well also be in the same region.

Somehow there should be a more hollistic appraoch to priority allocations. Perhaps a priority allocation should be one with infinite weight but still subject to the rules of the balanced allocator.

@hsanjuan hsanjuan added need/triage Needs initial labeling and prioritization kind/enhancement A net-new feature or improvement to an existing feature exp/expert Having worked on the specific codebase is important and removed need/triage Needs initial labeling and prioritization labels Sep 16, 2022
@hsanjuan hsanjuan added the P1 High: Likely tackled by core team if no one steps up label Sep 16, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
exp/expert Having worked on the specific codebase is important kind/enhancement A net-new feature or improvement to an existing feature P1 High: Likely tackled by core team if no one steps up
Projects
None yet
Development

No branches or pull requests

1 participant