Allocations to priority peers result in inbalances #1764
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
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.
The text was updated successfully, but these errors were encountered: