ngx_http_upstream_round_robin.c

[Maxim Dounin]

Hello!

On Wed, May 16, 2018 at 06:13:12PM +0000, Adam Horvath wrote:

> Yes our proxy_next_upstream is set. Below is our config. 
> 
> From the logging at:
> https://github.com/nginx/nginx/blob/master/src/http/ngx_http_upstream_round_robin.c#L594
> 
> We got maybe 50/second of these in our loop:
> 2018/05/16 17:26:34 [debug] 23317#0: *452 free rr peer 1 0
> 2018/05/16 17:26:34 [debug] 23317#0: *452 free rr peer 2 2
> 2018/05/16 17:26:34 [debug] 23317#0: *452 free rr peer 1 0
> 2018/05/16 17:26:34 [debug] 23317#0: *452 free rr peer 2 2
> 2018/05/16 17:26:34 [debug] 23317#0: *452 free rr peer 1 0
> 2018/05/16 17:26:34 [debug] 23317#0: *452 free rr peer 2 2
> Etc...
> 
> Which led me to speculate around: state == 2 == NGX_PEER_NEXT
> 
> I must also mention that our application is deeply entangled 
> with callbacks into http_request, so it is possible that we have 
> messed up there but I am following this lead for the moment. I 
> am at the moment trying to see the same error with our config 
> and a "vanilla nginx" but I am having build problems : (  
> 
> And we are actually using VERSION nginx-1.11.6... our build 
> pipeline is not [yet] quite accommodated to changing nginx 
> versions, sorry.

I don't think there are any related changes since 1.11.6, so 
testing with nginx 1.11.6 should be enough.  If you'll be able to 
reproduce the problem with vanilla nginx without any modifications 
/ external modules, please share details.

-- 
Maxim Dounin
http://mdounin.ru/