Skip to content

3.x: Fix LWT routing #383

@dkropachev

Description

@dkropachev

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.

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions