Here's how I would do it based on the cookie named backend:
- create a generic upstream with all your backends
- create specific upstreams for each of your backends
- create a map based on the cookie value (you can use any variable here,
not just cookies if you want to) which will select the sticky upstream,
and defaults to the generic upstream.
For example:
upstream generic {
server 127.0.0.1:8081;
server 127.0.0.1:8082;
server 127.0.0.1:8083;
}
upstream sticky8081 {
server 127.0.0.1:8081;
}
upstream sticky8082 {
server 127.0.0.1:8082;
}
upstream sticky8083 {
server 127.0.0.1:8083;
}
map $cookie_backend $sticky_backend {
default generic;
"1" sticky8081;
"2" sticky8082;
"3" sticky8083;
}
your proxy_pass directive will be
...
proxy_pass
http://$sticky_backend;...
When you create a new session, you set the backend cookie with the value
assigned to your backend (1, 2 or 3 in this example), and further requests
will be proxied to that backend.
If you don't want to use cookies, then any nginx variable should work. For
example an url parameter named backend would be:
map $arg_backend $sticky_backend {
...
or the request url:
map $uri $sticky_backend {
... (note that you can use regular expressions here)
Levente
On Fri, 24 Oct 2014, Torsten Bergmann wrote:
_______________________________________________
seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
Locked
