adding sequential policy to forward plugin (#1704)

* adding sequential policy to forward plugin

* making sequential an alias to first in proxy plugin
This commit is contained in:
Scott Donovan
2018-04-20 01:07:58 -05:00
committed by Miek Gieben
parent 26d1432ae6
commit 19a1ef48f2
8 changed files with 23 additions and 5 deletions

View File

@@ -25,7 +25,7 @@ However, advanced features including load balancing can be utilized with an expa
~~~
proxy FROM TO... {
policy random|least_conn|round_robin|first
policy random|least_conn|round_robin|sequential
fail_timeout DURATION
max_fails INTEGER
health_check PATH:PORT [DURATION]
@@ -39,7 +39,7 @@ proxy FROM TO... {
* **TO** is the destination endpoint to proxy to. At least one is required, but multiple may be
specified. **TO** may be an IP:Port pair, or may reference a file in resolv.conf format
* `policy` is the load balancing policy to use; applies only with multiple backends. May be one of
random, least_conn, round_robin or first. Default is random.
random, least_conn, round_robin or sequential. Default is random.
* `fail_timeout` specifies how long to consider a backend as down after it has failed. While it is
down, requests will not be routed to that backend. A backend is "down" if CoreDNS fails to
communicate with it. The default value is 2 seconds ("2s").
@@ -64,7 +64,8 @@ There are four load-balancing policies available:
* `random` (default) - Randomly select a backend
* `least_conn` - Select the backend with the fewest active connections
* `round_robin` - Select the backend in round-robin fashion
* `first` - Select the first available backend looking by order of declaration from left to right
* `sequential` - Select the first available backend looking by order of declaration from left to right
* `first` - Deprecated. Use sequential instead
All polices implement randomly spraying packets to backend hosts when *no healthy* hosts are