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
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
be appreciated.
Thanks,
-Daniel
On Nov 28, 2014, at 4:09 AM, Baptiste bed...@gmail.com wrote:
On Tue, Nov 25, 2014 at 6:56 AM, Daniel Lieberman
dlieber...@bitpusher.com wrote:
We're managing a fairly high-traffic site and we're seeing a lot of HTTP
503s with termination state SQ. I'm trying
servers are having issues. Our main goals here
are to learn what we can about the app server behavior, and to figure out what
we can do in HAproxy to mitigate the issues until the developers manage to fix
them.)
Thanks,
-Daniel
Daniel Lieberman
BitPusher, LLC
5 matches
Mail list logo
