periodic k-choices rebalancing
update node ID validity check to allow different vserver IDs
update node ID validity check to allow different vserver IDs
Turns out that no interval checking needed to be done, because each RemoteNodeState sent with every request inludes the ID of the sending vserver. So no trying out of all the vservers is needed.
Still did a bit of cleanup and refactoring ¯_(ツ)_/¯
adjust
isJoined
to kchoices semantics
interface between DHT and Service to request load information
try all possible vservers when bootstrap joining
try all possible vservers when bootstrap joining
adjust
isJoined
to kchoices semantics
refactor vs joining to always use
fediChordJoinNewVs
update node ID validity check to allow different vserver IDs