Re: [users@httpd] Retry connection to reverse proxy backend
Alright, I get the point. Making the connection more stable isn't going to work or happen inside of Apache. So my question is probably answered, you can close this case. (Oh, no case management in place, just a bunch of comments.) More off-topic: Mailing list defenders usually can't come up with advantages while I can easily name several disadvantages. Getting on-board is the hardest. Lists may be convenient for regulars, but are horror for occasional help-seekers. Registration and organising things to actually find the response takes too many steps and minutes. Sadly, nobody cares. It was good in the 80s, no need to change that. Of course I'm not deleting messages of my own thread, just all the others I have no use for. Moving to modern and usable web platforms next time... Just thought the official channel would know more on the topic. Yves Von: Yann Ylavic Gesendet: Mo, 2018-02-12 10:47 +0100 On Mon, Feb 12, 2018 at 10:24 AM, Yves Goergen wrote: One more of those unpractical mailing lists... (I'm already deleting 99% of what I receive to ask a single question. This is more than the spam.) One more of those users who think their issues should be resolved the way they think... Dropping packets is a very hard measure and will affect the entire web server, not just that single site. So it's not possible at all. Waiting in the proxy/server to retry connections after a delay is also going to affect an entire proxy/server (with limited resources). The proxy/server doesn't look like the right place to retain connections, this is more a "network" job IMHO. I'd DROP before the proxy during maintainance though, browers know if they can reconnect and/or resend requests on failure, proxy don't. Feel free to => delete ;) Regards, Yann. - To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org For additional commands, e-mail: users-h...@httpd.apache.org - To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org For additional commands, e-mail: users-h...@httpd.apache.org
Re: [users@httpd] Retry connection to reverse proxy backend
On Mon, Feb 12, 2018 at 10:24 AM, Yves Goergen wrote: > One more of those unpractical mailing lists... (I'm already deleting 99% of > what I receive to ask a single question. This is more than the spam.) One more of those users who think their issues should be resolved the way they think... > > Dropping packets is a very hard measure and will affect the entire web > server, not just that single site. So it's not possible at all. Waiting in the proxy/server to retry connections after a delay is also going to affect an entire proxy/server (with limited resources). The proxy/server doesn't look like the right place to retain connections, this is more a "network" job IMHO. I'd DROP before the proxy during maintainance though, browers know if they can reconnect and/or resend requests on failure, proxy don't. Feel free to => delete ;) Regards, Yann. - To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org For additional commands, e-mail: users-h...@httpd.apache.org
Re: [users@httpd] Retry connection to reverse proxy backend
One more of those unpractical mailing lists... (I'm already deleting 99% of what I receive to ask a single question. This is more than the spam.) Okay, so I'm not going to solve this problem server-side. The client that gets the error will have to retry on its own more often and even resend its POST data. And users will have to live with the error message they might see and learn to work around it. Not nice but certainly possible. Dropping packets is a very hard measure and will affect the entire web server, not just that single site. So it's not possible at all. Yves Von: Marat Khalili Gesendet: Mo, 2018-02-12 04:56 +0100 If your upgrade procedure is indeed "a second", I'd try to DROP with iptables SYN packets from proxy to appserver for this period, proxy will likely retry connection attempts. Depends on many factors, but at least worths a try. Where can I request that feature to be considered for adding? On developers, not users maillist? With a patch ready or a bounty for implementation? What solutions do you have for this issue? Most users will just reload the page upon seeing 503 error. Applications need to be taught case-by-case, since not all operations are sensible or safe to retry. That's going to be a problem when you discuss automating it unconditionally with developers. - To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org For additional commands, e-mail: users-h...@httpd.apache.org
Re: [users@httpd] Retry connection to reverse proxy backend
If your upgrade procedure is indeed "a second", I'd try to DROP with iptables SYN packets from proxy to appserver for this period, proxy will likely retry connection attempts. Depends on many factors, but at least worths a try. > Where can I request that feature to be considered for adding? On developers, not users maillist? With a patch ready or a bounty for implementation? > What solutions do you have for this issue? Most users will just reload the page upon seeing 503 error. Applications need to be taught case-by-case, since not all operations are sensible or safe to retry. That's going to be a problem when you discuss automating it unconditionally with developers. -- With Best Regards, Marat Khalili - To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org For additional commands, e-mail: users-h...@httpd.apache.org
Re: [users@httpd] Retry connection to reverse proxy backend
From getting zero replies I think this isn't possible with Apache. Where can I request that feature to be considered for adding? It can increase the availability of websites. Doesn't that sound interesting? What solutions do you have for this issue? Or am I just thinking too small and everybody uses data centers with tons of servers and load balancers today? Yves Von: Yves Goergen Gesendet: Sa, 2018-02-03 16:08 +0100 Hello, I've configured Apache as a reverse proxy for my application server. When the backend server isn't available, Apache quickly responds the browser with an error 503. There are short downtimes while I'm upgrading the application server. But Apache doesn't even care to retry and make the connection request succeed maybe a few seconds later. It always raises error 503. Can I configure Apache to try a little harder, and if the backend isn't responding, wait a second and try again a couple times? That would make connections much more reliable and the client wouldn't have to deal with connection retrying so often. There's a "retry" option for the ProxyPass command but it has a different meaning. It just tells Apache to not retry until the number of seconds has elapsed. It might as well be named "dontretrybefore". I'm looking for an option that could be named "retryconnect". Yves Goergen http://unclassified.software - To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org For additional commands, e-mail: users-h...@httpd.apache.org - To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org For additional commands, e-mail: users-h...@httpd.apache.org
[users@httpd] Retry connection to reverse proxy backend
Hello, I've configured Apache as a reverse proxy for my application server. When the backend server isn't available, Apache quickly responds the browser with an error 503. There are short downtimes while I'm upgrading the application server. But Apache doesn't even care to retry and make the connection request succeed maybe a few seconds later. It always raises error 503. Can I configure Apache to try a little harder, and if the backend isn't responding, wait a second and try again a couple times? That would make connections much more reliable and the client wouldn't have to deal with connection retrying so often. There's a "retry" option for the ProxyPass command but it has a different meaning. It just tells Apache to not retry until the number of seconds has elapsed. It might as well be named "dontretrybefore". I'm looking for an option that could be named "retryconnect". Yves Goergen http://unclassified.software - To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org For additional commands, e-mail: users-h...@httpd.apache.org
