Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

3.x: Fix LWT routing #383

Open
dkropachev opened this issue Nov 26, 2024 · 0 comments
Open

3.x: Fix LWT routing #383

dkropachev opened this issue Nov 26, 2024 · 0 comments

Comments

@dkropachev
Copy link
Collaborator

Currently LWT routing does not involve LoadBlancingPolicy at all

} else if (statement.isLWT()) {
this.queryPlan =
new QueryPlan(
getReplicas(
manager.poolsState.keyspace,
statement,
manager
.loadBalancingPolicy()
.newQueryPlan(manager.poolsState.keyspace, statement)));

And returns vnode/tablet replicas as they are.
As result if user configured cluster with TokenAwarePolicy+DCAwareRoundRobinPolicy/RackAwareRoundRobinPolicy as LoadBalancingPolicy they expect to see queries routed to a particular DC, but driver voids rack/dc awarness and route traffic to first replica first, which could be from another Dc/Rack.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant