Can't tell atm. if a timeout forces a node to become offline but 60s is
still along time to wait (and decide) without actually knowing if a node is
overloaded (it might be just busy which does not always mean overloaded).
There are tools for fi. edge routers which polls a status page to decide to
Thanks itpp2012, I'll look at LUA
if I understand correctly, we can not specify the timeout of the session to
upstream the server, initiate a timeout error, and force requests to move to
another server?
proxy_read_timeout 1;
-> proxy_next_upstream error timeout
Posted at Nginx Forum:
https
You may have to resort to Lua (openresty) and periodically perform via a sub
request a query which should indicate how fast an upstream is and decide
weather to take it offline (which also can be done with Lua).
Posted at Nginx Forum:
https://forum.nginx.org/read.php?2,280259,280260#msg-280260
_
