public class TokenAwarePolicy extends Object implements ChainableLoadBalancingPolicy, CloseableLoadBalancingPolicy
This policy encapsulates another policy. The resulting policy works in the following way:
distance method is inherited from the child policy.newQueryPlan method will first
return the LOCAL replicas for the query (based on Statement.getRoutingKey())
if possible (i.e. if the query getRoutingKey method
doesn't return null and if Metadata.getReplicas(java.lang.String, java.nio.ByteBuffer)
returns a non empty set of replicas for that partition key). If no
local replica can be either found or successfully contacted, the rest
of the query plan will fallback to one of the child policy.
Do note that only replica for which the child policy distance
method returns HostDistance.LOCAL will be considered having
priority. For example, if you wrap DCAwareRoundRobinPolicy with this
token aware policy, replicas from remote data centers may only be
returned after all the host of the local data center.
| Constructor and Description |
|---|
TokenAwarePolicy(LoadBalancingPolicy childPolicy)
Creates a new
TokenAware policy with shuffling of replicas. |
TokenAwarePolicy(LoadBalancingPolicy childPolicy,
boolean shuffleReplicas)
Creates a new
TokenAware policy. |
| Modifier and Type | Method and Description |
|---|---|
void |
close()
Gets invoked at cluster shutdown.
|
HostDistance |
distance(Host host)
Return the HostDistance for the provided host.
|
LoadBalancingPolicy |
getChildPolicy()
Returns the child policy.
|
void |
init(Cluster cluster,
Collection<Host> hosts)
Initialize this load balancing policy.
|
Iterator<Host> |
newQueryPlan(String loggedKeyspace,
Statement statement)
Returns the hosts to use for a new query.
|
void |
onAdd(Host host)
Called when a new node is added to the cluster.
|
void |
onDown(Host host)
Called when a node is determined to be down.
|
void |
onRemove(Host host)
Called when a node is removed from the cluster.
|
void |
onSuspected(Host host)
Called when a node is suspected to be dead.
|
void |
onUp(Host host)
Called when a node is determined to be up.
|
public TokenAwarePolicy(LoadBalancingPolicy childPolicy, boolean shuffleReplicas)
TokenAware policy.childPolicy - the load balancing policy to wrap with token awareness.shuffleReplicas - whether to shuffle the replicas returned by getRoutingKey.
Note that setting this parameter to true might decrease the
effectiveness of caching (especially at consistency level ONE), since
the same row will be retrieved from any replica (instead of only the
"primary" replica without shuffling).
On the other hand, shuffling will better distribute writes, and can
alleviate hotspots caused by "fat" partitions.public TokenAwarePolicy(LoadBalancingPolicy childPolicy)
TokenAware policy with shuffling of replicas.childPolicy - the load balancing policy to wrap with token
awareness.TokenAwarePolicy(LoadBalancingPolicy, boolean)public LoadBalancingPolicy getChildPolicy()
ChainableLoadBalancingPolicygetChildPolicy in interface ChainableLoadBalancingPolicypublic void init(Cluster cluster, Collection<Host> hosts)
LoadBalancingPolicyNote that the driver guarantees that it will call this method exactly once per policy object and will do so before any call to another of the methods of the policy.
init in interface LoadBalancingPolicycluster - the Cluster instance for which the policy is created.hosts - the initial hosts to use.public HostDistance distance(Host host)
distance in interface LoadBalancingPolicyhost - the host of which to return the distance of.host as returned by the wrapped policy.public Iterator<Host> newQueryPlan(String loggedKeyspace, Statement statement)
The returned plan will first return replicas (whose HostDistance
for the child policy is LOCAL) for the query if it can determine
them (i.e. mainly if statement.getRoutingKey() is not null).
Following what it will return the plan of the child policy.
newQueryPlan in interface LoadBalancingPolicystatement - the query for which to build the plan.loggedKeyspace - the currently logged keyspace (the one set through either
Cluster.connect(String) or by manually doing a USE query) for
the session on which this plan need to be built. This can be null if
the corresponding session has no keyspace logged in.public void onUp(Host host)
Host.StateListeneronUp in interface Host.StateListenerhost - the host that has been detected up.public void onSuspected(Host host)
Host.StateListener
A node is suspected to be dead when an error occurs on one of it's
opened connection. As soon as an host is suspected, a connection attempt
to that host is immediately tried. If this succeed, then it means that
the connection was disfunctional but that the node was not really down.
If this fails however, this means the node is truly dead, onDown() is
called and further reconnection attempts are scheduled according to the
ReconnectionPolicy in place.
When this event is triggered, it is possible to call the host
Host.getInitialReconnectionAttemptFuture() method to wait until the
initial and immediate reconnection attempt succeed or fail.
Note that some StateListener may ignore that event. If a node that
that is suspected down turns out to be truly down (that is, the driver
cannot successfully connect to it right away), then Host.StateListener.onDown(com.datastax.driver.core.Host) will
be called.
onSuspected in interface Host.StateListenerpublic void onDown(Host host)
Host.StateListeneronDown in interface Host.StateListenerhost - the host that has been detected down.public void onAdd(Host host)
Host.StateListenerThe newly added node should be considered up.
onAdd in interface Host.StateListenerhost - the host that has been newly added.public void onRemove(Host host)
Host.StateListeneronRemove in interface Host.StateListenerhost - the removed host.public void close()
CloseableLoadBalancingPolicyclose in interface CloseableLoadBalancingPolicyCopyright © 2015. All rights reserved.