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, Kaustubhby kaustubh - Nginx Mailing List - English
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_http_proxy_module.html#proxy_request_buffering "When buffering is disabled, the request bby kaustubh - Nginx Mailing List - English
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 early 503 from first upstream.by kaustubh - Nginx Mailing List - English
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.deo@gmail.com> wrote: > Hi, > > We are using nginx as reverse proxy and have a set of upstream servers > configured > with upstream next enabled for feby kaustubh - Nginx Mailing List - English
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 localhost:8081; server localhost:8082; } server { ... location / { proxy_pass htby kaustubh - Nginx Mailing List - English
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 localhost:8081; server localhost:8082; } server { ... location / { proxy_pass htby kaustubh - Nginx Development
Thanks Jeff for the reference, will have a look! _______________________________________________ nginx-devel mailing list nginx-devel@nginx.org http://mailman.nginx.org/mailman/listinfo/nginx-develby kaustubh - Nginx Development
Thanks Yichun and Jeff for your inputs and sorry for late ack. I had a brief look at ngx_drizzle, I see that it needs the library to expose underlying fd, which is not possible in our case, but looks an interesting solution. The other cosocket API mechanism seem to be using unix domain socket as per the docs, so this would be similar to using pipe/socket to handle async apis where the callback coby kaustubh - Nginx Development