c5592ee3be
Previously we only exposed the use of a single URL for LDAP realms, while the code supported multiple URLs. Internally we always used a failover server set, which would have provided failover to another LDAP server if multiple existed. This change introduces a new setting `load_balance.type` on the realm that indicates the type of load balancing. Valid options are: * `failover` - the first server in the list will be used until it fails and then additional servers will be tried until one succeeds. The first successful server will be used from now on. This is the default. * `round_robin` - continuously iterates through the list of servers for each new connection. If a server is down, the iteration will continue until a successful connection is made. The downfall here is that the list does not get reordered on a down server, so there is overhead for always trying the servers in order. * `dns_failover` - This server set takes a single URL that uses a DNS that will resolve to multiple IP addresses. Connections will be consistently attempted to servers in the order they are retrieved from the name service; there is no re-ordering and the first successful connection will be used. * `dns_round_robin` - This server set takes a single URL that uses a DNS that will resolve to multiple IP addresses. The addresses retrieved from the name service will connected to in the same order as `round_robin`. Closes elastic/elasticsearch#31 Original commit: elastic/x-pack-elasticsearch@9ce9a1bf23 |
||
|---|---|---|
| .. | ||
| license | ||
| qa | ||
| x-dev-tools | ||
| x-pack | ||
| build.gradle | ||