rits Wrote:
-------------------------------------------------------
> Thank you for your response. I am new to nginx, can you elaborate or
> send a link to using Lua with nginx sticky module(for windows).
See our manual "NGINX for Windows - The Latest Documentation" at http://nginx-win.ecsds.eu/ chapter 18.
Adding Lua for upstream checks: https://github.com/openresty/lua-resty-upstream-healthcheck
> I need back up option so that in case 1 server becomes unavailable,
> all subsequest new requests go to available servers. My upstream
> application already handles unavailable sessions.
Then leave the upstream as it is, when a member is down nginx will mark it as such (down), ea. refrain from using 'backup'.
> Also, is it possible to use the generic hashing to send all requests
> to same server for stickiness, using my upstream address?
>
> upstream myLoadBalancer {
> hash $upstream_addr;
> server remote1:port1;
> server remote1:port2;
> server remote2.:port1;
> }
> Is something like above possible?
Should be possible, the only way to know is to test this to make sure the 'client' really is 'stuck' to the same member.
-------------------------------------------------------
> Thank you for your response. I am new to nginx, can you elaborate or
> send a link to using Lua with nginx sticky module(for windows).
See our manual "NGINX for Windows - The Latest Documentation" at http://nginx-win.ecsds.eu/ chapter 18.
Adding Lua for upstream checks: https://github.com/openresty/lua-resty-upstream-healthcheck
> I need back up option so that in case 1 server becomes unavailable,
> all subsequest new requests go to available servers. My upstream
> application already handles unavailable sessions.
Then leave the upstream as it is, when a member is down nginx will mark it as such (down), ea. refrain from using 'backup'.
> Also, is it possible to use the generic hashing to send all requests
> to same server for stickiness, using my upstream address?
>
> upstream myLoadBalancer {
> hash $upstream_addr;
> server remote1:port1;
> server remote1:port2;
> server remote2.:port1;
> }
> Is something like above possible?
Should be possible, the only way to know is to test this to make sure the 'client' really is 'stuck' to the same member.