PickNextMember needs to be updated to have tag awareness
Closed this issue · 2 comments
dselans commented
While implementing locality, I completely forgot that on top of check (re)distribution during member join/leaves, check pinning logic also needs to occur when checks are added/removed from the system.
Ooops.
dselans commented
This is not trivial -- while I was able to update PickNextMember, several other pieces need to be refactored to account for the fact that an existing check may now be required to be pinned to a specific node. This means that handleCheckConfigChange needs a facelift.