On Fri, Dec 5, 2014 at 7:20 PM, Daniel Lieberman
dlieber...@bitpusher.com wrote:
On Dec 5, 2014, at 5:21 AM, Baptiste bed...@gmail.com wrote:
On Thu, Dec 4, 2014 at 11:50 PM, Daniel Lieberman
dlieber...@bitpusher.com wrote:
We have a situation where our app servers sometimes get into a bad
Hi Daniel,
We have a situation where our app servers sometimes get into a bad
state, and hitting a working server is more important than enforcing
persistence. Generally the number of connections to a bad server
grows rapidly, so we’ve set a maxconn value on the server line which
Lukas Tribus wrote on 12/05/2014 12:09 PM:
[CUT]
You should work on your health checking and implement it in a way
that HAProxy can detect bad servers. That is the proper way to
deal with such problems.
Sometimes, providing a helper script on the backend that detects any
problems can help with
On Thu, Dec 4, 2014 at 11:50 PM, Daniel Lieberman
dlieber...@bitpusher.com wrote:
We have a situation where our app servers sometimes get into a bad state, and
hitting a working server is more important than enforcing persistence.
Generally the number of connections to a bad server grows
On Dec 5, 2014, at 5:21 AM, Baptiste bed...@gmail.com wrote:
On Thu, Dec 4, 2014 at 11:50 PM, Daniel Lieberman
dlieber...@bitpusher.com wrote:
We have a situation where our app servers sometimes get into a bad state,
and hitting a working server is more important than enforcing persistence.
Why is this wrong?
We do use health-checking, but we can generate a lot of 503s in 2s. Of course
the best answer is to fix the app server code so we don’t see this, but the
developers have been working on this for a while and we’re trying to mitigate
in the meantime.
More frequent health
Daniel Lieberman wrote on 2014-12-05 19:29:
Why is this wrong?
We do use health-checking, but we can generate a lot of 503s in 2s.
Of course the best answer is to fix the app server code so we don’t
see this, but the developers have been working on this for a while
and we’re trying to
We have a situation where our app servers sometimes get into a bad state, and
hitting a working server is more important than enforcing persistence.
Generally the number of connections to a bad server grows rapidly, so we’ve set
a maxconn value on the server line which effectively takes a
8 matches
Mail list logo
