On Thu, Feb 2, 2012 at 12:05 AM, Rick Richardson
<rick.richardson@gmail.com> wrote:
> Sorry for the confusion. I don't want failover/backup for redis servers, I
> want the redis request to return multiple upstreams that I can proxy to with
> proxy_pass.
>
> E.g. I get a request for Foo.com. I ask redis for a list of upstream servers
> to which I can serve Foo.com.  I then feed the entire list somehow into
> proxy_pass.  It then performs its normal htttp_upstream operation as if it
> had a standard list of peers in an upstream.
>

Sorry for the misunderstanding :)

I think we could just patch ngx_proxy and mimic
ngx_http_upstream_create_round_robin_peer to dynamically construct a
peer list for the current request, just like how ngx_proxy does now
for multiple A records corresponding to a single host name if the
dynamic resolver is used. You can have a try ;)

Maybe it makes sense to provide a generic interface for ngx_proxy to
make such things easy.

Best regards,
-agentzh

_______________________________________________
nginx-devel mailing list
nginx-devel@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx-devel