True, You are right.
The issue I am facing is
upstream myLoadBalancer {
> hash $upstream_addr;
> server remote1:port1;
> server remote1:port2;
> server remote2.:port1;
> }
say first server is selected from upstream. Since I have specified hash $upstream_addr, all subsequent requests go to this server. Even new requests. There is no new cookie or parameter to change it to next server for new set of stateful requests.
I think that is how generic hash works(not cookie based), dependiong on either request IP, request parameter, it sticks to a backend server.
So looks like not ideal in my scenario.
For Lua: https://github.com/openresty/lua-resty-upstream-healthcheck,
Is it available in nginx version 1.9, or it requires adding another module?
The issue I am facing is
upstream myLoadBalancer {
> hash $upstream_addr;
> server remote1:port1;
> server remote1:port2;
> server remote2.:port1;
> }
say first server is selected from upstream. Since I have specified hash $upstream_addr, all subsequent requests go to this server. Even new requests. There is no new cookie or parameter to change it to next server for new set of stateful requests.
I think that is how generic hash works(not cookie based), dependiong on either request IP, request parameter, it sticks to a backend server.
So looks like not ideal in my scenario.
For Lua: https://github.com/openresty/lua-resty-upstream-healthcheck,
Is it available in nginx version 1.9, or it requires adding another module?