On Thu, Mar 17, 2011 at 02:45:27PM -0500, Shaw, Christopher wrote:
Willy,
I thought I had come up with a working config file, but the
server persistence still isn't behaving properly. If a server is down,
or has its weight dropped to 0, a user is unable to reconnect to their
session
On Wed, Mar 16, 2011 at 10:30:59AM -0400, Les Stroud wrote:
I have a situation where this may be useful, but I want to make sure I
understand. In this particular case, if the user cannot be serviced by a
backend server, I need them to logout and log back in (too much crap stored
in
Hey,
You can also play with /proc/sys/vm/swapiness to avoid / limit swapping...
But as explained, it's a bad idea to let a lot balancer swapping. It's
supposed to introduce a very very low delay and swapping would
increase that delay.
Just ensure you have enough memory to handle the load you
Hi all,
Actually I asked this question because I saw a lot of times systems that had
more than 10Gb of free physical memory and they anyway used swap
partition(about 1-5 Mb). I saw that happened on FreeBSD and on Linux, so I
thought it's possible to see that again when I'll run HAProxy.
And I
On 19 March 2011 10:58, Antony ddj...@mail.ru wrote:
Hi all,
Actually I asked this question because I saw a lot of times systems that had
more than 10Gb of free physical memory and they anyway used swap
partition(about 1-5 Mb). I saw that happened on FreeBSD and on Linux, so I
thought
Is there a way to rate limit per IP (or CDIR)? In the sense our
global capacity (rate limit sessions) might be x requests/sec,
but to protect against abusive bots or DOS attacks we would to
also limit any IP or ideally some bigger buckets like a CDIR to
say x/100 requests/sec.
/Allan
--
6 matches
Mail list logo
