Behavior between upstream hash and backup

Jonathan Simowitz simowitz at google.com
Thu Jan 12 15:03:47 UTC 2017


Thank you Maxim; that is exactly the detailed response I was looking for.
If possible I would recommend updating the docs to clarify this for others.
http://nginx.org/en/docs/http/ngx_http_upstream_module.html#hash

~Jonathan

On Thu, Jan 12, 2017 at 9:44 AM, Maxim Dounin <mdounin at mdounin.ru> wrote:

> Hello!
>
> On Wed, Jan 11, 2017 at 04:27:51PM -0500, Jonathan Simowitz via nginx
> wrote:
>
> > Hello,
> >
> > I would like to define an upstream block with a number of servers and
> > utilize the hash directive to choose a particular server dependent on the
> > request. There is a chance that the chosen server could fail and so I
> would
> > also like to configure a backup server to handle the request in this
> case.
>
> If there are more than one server in the upstream block, the
> default behaviour is to try another server if a choosen one fails,
> see http://nginx.org/r/proxy_next_upstream.  The exact algorithm
> to select "another server" varies depending on the balancing
> algorithm used - e.g., in case of "hash .. consistent" it means
> selecting the next point in the continuum, like if the failed
> server was removed from the list.
>
> > If I define an additional server in this upstream and declare it as
> backup
> > will it handle the request if the hash-chosen server fails as defined by
> my
> > proxy_next_upstream directive?
>
> No, backup servers are not supported by the hash balancer.
>
> --
> Maxim Dounin
> http://nginx.org/
>



-- 
Jonathan Simowitz | Jigsaw |  Software Engineer |  simowitz at google.com |
 631-223-8608
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.nginx.org/pipermail/nginx/attachments/20170112/1204df74/attachment.html>


More information about the nginx mailing list