Regarding proxy_next_upstream parameter

[Pankaj Kaushik]

Hi,

I am trying to do failover as per below configuration :-

upstream backend {
                hash $key2 consistent;
                server 10.0.0.22:8080;
                server 10.0.0.23:8080;
                server 10.0.0.24:8080;
                server 10.0.0.25:8080;
                server 10.0.0.26:8080;
        }
        upstream backend_2 {
                server 10.0.0.22:8080;
                server 10.0.0.23:8080;
                server 10.0.0.24:8080;
                server 10.0.0.25:8080;
                server 10.0.0.26:8080;
        }

            server {
                listen 90 default_server;

                location = / {
                   proxy_pass http://backend_2;
                   proxy_next_upstream error timeout http_404;
                }
                location / {
                   proxy_pass http://backend;
                   proxy_next_upstream error timeout http_404;
                }

        }

In error logs i received following message :-

2014/08/10 09:52:16 [info] 514#0: *184 epoll_wait() reported that client
prematurely closed connection, so upstream connection is closed too while
sending request to upstream, client: 14.102.112.84, server: , request: "GET
/mybucket4/ HTTP/1.1", upstream: "http://10.0.0.23:8080/mybucket4/", host: "
65.60.72.19:90"


Can any body help me on this ?

Thanks,
Panky
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.nginx.org/pipermail/nginx/attachments/20140810/5a4b044f/attachment.html>