Behavior between upstream hash and backup

[Jonathan Simowitz]

Hi Robert,

Thank you for your reply. Yes, I have taken the backup parameter into
account. It is not clear to me how the backup parameter works in
combination with the hash directive and whether this achieves the desired
behavior.

~Jonathan

On Wed, Jan 11, 2017 at 4:34 PM, Robert Paprocki <
rpaprocki at fearnothingproductions.net> wrote:

> Hi,
>
> On Wed, Jan 11, 2017 at 1:27 PM, Jonathan Simowitz via nginx <
> nginx at nginx.org> 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 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?
>>
>
> Have you had a look at the 'backup' parameter of http://nginx.org/en/docs/
> http/ngx_http_upstream_module.html#server? Sounds like exactly what you
> need.
>
>
> _______________________________________________
> nginx mailing list
> nginx at nginx.org
> http://mailman.nginx.org/mailman/listinfo/nginx
>



-- 
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/20170111/e8b580c2/attachment.html>