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.
Migrated to Jira: DRIVER-143
Currently LWT routing does not involve
LoadBlancingPolicyat alljava-driver/driver-core/src/main/java/com/datastax/driver/core/RequestHandler.java
Lines 146 to 154 in dbfe82a
And returns vnode/tablet replicas as they are.
As result if user configured cluster with
TokenAwarePolicy+DCAwareRoundRobinPolicy/RackAwareRoundRobinPolicyasLoadBalancingPolicythey 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.Migrated to Jira: DRIVER-143