upstream - behavior on pool exhaustion

[B.R.]

On Wed, Apr 19, 2017 at 10:51 AM, Ruslan Ermilov <ru at nginx.com> wrote:

> And what about the next request when all of servers are either "down"
> or "unavailable"?
>

To me, all the unavailable servers have been 'tried', ie their state has
been checked, as the docs
<http://nginx.org/en/docs/http/ngx_http_upstream_module.html#upstream> say
every server of an upstream group will be checked.
Thus, they should all appear, along with the time it took for that lookup
to be made (usually 0.000 since no communication occurred and a simple
internal check has probably been made for the duration of the 'unavailable'
state).

​No special value whatsoever, as none required, and the grammar of the 2
variables is stable.​
​If an explicit message about attempts against completely unavailable
upstream groups should be logged, it would be so in the error log.​

---
*B. R.*
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.nginx.org/pipermail/nginx/attachments/20170419/0db60f5d/attachment.html>