файл конфигурации для lloadd, автономного демона LDAP (configuration file for lloadd, the stand-alone LDAP daemon)
TIER OPTIONS
tier <tier type>
Groups servers which should be considered in the same try.
If a viable connection is found even if busy, the load
balancer does not proceed to the next tier. The process of
selection a connection within a tier depends on the tier's
type.
Available types are:
roundrobin
Servers are tried in order and if one is selected
successfully, the following search will try from the one
next on the list.
weighted
Backend servers accept a new option weight=<int> which
indicates how often it should be selected. If unspecified,
weight defaults to 0 and such backends have a slight
chance of being selected even when a non-zero weight
backend is configured in the tier. The selection process
is along the lines of RFC2782.
bestof Like with weighted, backends accept the weight=<int>
option. Average latency multiplied by weight is measured
over time. The selection process chooses 2 backends at
random, compares their weighted latencies and the backend
with a better (lower) score is tried. If the backend is
not available (or is busy), the other backend is tried,
then backends are chosen in a round-robin order.
Note that unlike weighted, the higher the weight, the
higher the "effective" latency and lower the chance a
backend is selected.
