This repository was archived by the owner on Aug 26, 2024. It is now read-only.
Add rack-aware load balancing policy #2
Merged
Conversation
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
The out was not helpful for understanding the failure of a test. Printing the query plans will help.
This argument was not used anywhere, it worked by chance since it had the same value everywhere.
The Datstax C++ driver has default ONE, the Scylla fork has LOCAL_ONE.
martin-sucha
force-pushed
the
ms/rack-aware-cleanup
branch
from
e69b80e to
f59881a
Compare
|
Some unit tests are failing, but those are failing also upstream. All load balancing policy unit tests pass ( |
xnavratil
reviewed
Jan 2, 2023
We need to prefer local rack as there are higher network costs when communicating with nodes in remote rack. This policy prefers nodes from the local rack, then local datacenter and then other nodes. The new RackAwarePolicy is similar to DCAwarePolicy, but does not have the deprecated options. TokenAwarePolicy and other code needed to be modified so that the local rack is propagated. The TokenAware policy was changed to prefer replicas in remote rack / remote DC before trying non-replica nodes. It does not make much sense to not try the replicas and trying the replicas simplifies the code as now we have three levels local/remote/remote2. This change might not be backwards-compatible, we don't know what exactly this project guarantees in terms of backwards compatibility. Co-Authored-By: Peter Navrátil <[email protected]>
martin-sucha
force-pushed
the
ms/rack-aware-cleanup
branch
from
f59881a to
a0d80ff
Compare
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
We need to prefer local rack as there are higher network costs
when communicating with nodes in remote rack.
This policy prefers nodes from the local rack, then local datacenter
and then other nodes.
The new RackAwarePolicy is similar to DCAwarePolicy,
but does not have the deprecated options.
TokenAwarePolicy and other code needed to be modified
so that the local rack is propagated.
The TokenAware policy was changed to prefer replicas in remote
rack / remote DC before trying non-replica nodes.
It does not make much sense to not try the replicas and
trying the replicas simplifies the code as now we have three
levels local/remote/remote2.
This change might not be backwards-compatible,
we don't know what exactly this project guarantees in terms of
backwards compatibility.
Co-Authored-By: Peter Navrátil [email protected]