The load balancing model used, according to the selected QoS is defined
by a number of different load balancing classes. These are configured
automatically when different QoS is selected, be explicitly changed by
altering the configuration file. The supported load balancers are
detailed in the table below:
| Load Balancer | Default QoS | Description |
|---|---|---|
| DefaultLoadBalancer |
RW_STRICT
| Always selects the Primary data source |
| MostAdvancedSlaveLoadBalancer |
RO_RELAXED
| Selects the Replica that has replicated the most events, by comparing data sources "high water" marks. If no Replica is available, the Primary will be returned. |
| LowestLatencySlaveLoadBalancer |
Selects the Replica data source that has the lowest replication
lag, or appliedLatency
in ls -l within
cctrl output. If no Replica data source is
eligible, the Primary data source will be selected.
| |
| RoundRobinSlaveLoadBalancer | Selects a Replica in a round robin manner, by iterating through them using internal index. Returns the Primary if no Replica is found online | |
| HighWaterSlaveLoadBalancer |
RW_SESSION
| Given a session high water (usually the high water mark of the update event), selects the first Replica that has higher or equal high water, or the Primary if no Replica is online or has replicated the given session event. This is the default used when SmartScale is enabled. |
The default setting is
MostAdvancedSlaveLoadBalancer.
To change the Connector load balancer, specify the property in the
configuration, i.e to use Round Robin, add the following to the
[defaults] stanza of your
/etc/tungsten/tungsten.ini and issue
tpm update:
property=dataSourceLoadBalancer_RO_RELAXED=com.continuent.tungsten.router.resource.loadbalancer.RoundRobinSlaveLoadBalanceror for staging deployments, issue the following from the staging server:
shell> ./tools/tpm update alpha \
--property=dataSourceLoadBalancer_RO_RELAXED=com.continuent.tungsten.router.resource.loadbalancer.RoundRobinSlaveLoadBalancer