Re: input required on proxy_next_upstream

2017-02-22 Thread kaustubh
Thanks again for detailed reply. Yeah it would have been good to have this feature in nginx upstream module. Its an important feature, will try out your suggestions and will share. Thanks a lot for sharing inputs! Cheers, Kaustubh Posted at Nginx Forum: https://forum.nginx.org/read.php?2,27244

Re: input required on proxy_next_upstream

2017-02-21 Thread Francis Daly
On Tue, Feb 21, 2017 at 04:45:09AM -0500, kaustubh wrote: Hi there, > Thanks Francis! I was able to test that above works. Good stuff -- at least we can see that things are fundamentally correct. > But problem is when we have proxy buffering off and when we try to send > large file say 1gb, it

Re: input required on proxy_next_upstream

2017-02-21 Thread kaustubh
Thanks Francis! I was able to test that above works. But problem is when we have proxy buffering off and when we try to send large file say 1gb, it fails with 502 without trying next instance. proxy_request_buffering off; proxy_http_version 1.1; Docs say so, http://nginx.org/en/docs/http/ngx_

Re: input required on proxy_next_upstream

2017-02-18 Thread Francis Daly
On Wed, Feb 15, 2017 at 10:47:56PM +0530, Kaustubh Deorukhkar wrote: Hi there, > For some reason this is not working. Can someone suggest if am missing > something? It seems to work fine for me as-is for GET and PUT. And not for POST. > proxy_next_upstream error timeout invalid_header htt

Re: input required on proxy_next_upstream

2017-02-17 Thread kaustubh
Thanks for reply. But I checked upstreams and second instance is working fine but does not receive retry request. I did small setup where one upstream instance responds early with 503 and other instance processes requests, and I observe that the request never comes to working upstream server on ea

Re: input required on proxy_next_upstream

2017-02-17 Thread Igor A. Ippolitov
Could it happen, that all servers reply with HTTP 503? I suggest you could extend your logs with upstream_status variable and if there is only one upstream reply status - try looking through error logs. On 15.02.2017 20:17, Kaustubh Deorukhkar wrote: Hi, We are using nginx as reverse proxy a

Re: input required on proxy_next_upstream

2017-02-17 Thread Kaustubh Deorukhkar
Hello, Any inputs on this? Is is supported to retry next upstream, if upstream server responds early rejecting request for any valid reason? Thanks, Kaustubh On Wed, Feb 15, 2017 at 10:47 PM, Kaustubh Deorukhkar < kaustubh@gmail.com> wrote: > Hi, > > We are using nginx as reverse proxy and

input required on proxy_next_upstream

2017-02-15 Thread Kaustubh Deorukhkar
Hi, We are using nginx as reverse proxy and have a set of upstream servers configured with upstream next enabled for few error conditions to try next upstream server. For some reason this is not working. Can someone suggest if am missing something? http { ... upstream myservice { server loc

Re: input required on proxy_next_upstream

2017-02-15 Thread Maxim Dounin
Hello! On Wed, Feb 15, 2017 at 01:27:53PM +0530, Kaustubh Deorukhkar wrote: > We are using nginx as reverse proxy and have a set of upstream servers > configured > with upstream next enabled for few error conditions to try next upstream > server. > For some reason this is not working. Can someone