Add availability zone awareness to node based routing#6189
Open
nadav-govari wants to merge 1 commit intonadav/feature-node-based-routingfrom
Open
Add availability zone awareness to node based routing#6189nadav-govari wants to merge 1 commit intonadav/feature-node-based-routingfrom
nadav-govari wants to merge 1 commit intonadav/feature-node-based-routingfrom
Conversation
nadav-govari
force-pushed
the
nadav/az-aware
branch
from
010844e to
0f78133
Compare
nadav-govari
force-pushed
the
nadav/az-aware
branch
from
0f78133 to
44c705e
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Uses the already broadcasted cluster-level property
availability_zoneto inform ingest decisions. Similar to the old shard based routing table, splits candidate nodes into local/remote vecs, and prefers to pick from same-AZ nodes before other-AZ nodes.This assumes that there is an equal distribution of traffic between AZs. If not, the AZ that sees more traffic will get hotter sooner, and will create a hotspot. For now, it's up to users to ensure that their traffic is load balanced across the cluster properly.
How was this PR tested?
Unit tests. end to end tests incoming.