Hi, My guess is that you have configured too huge buffers in HAProxy on in your TCP sysctls. There is no reason for HAProxy to use all the available memory, unless you're running a 1.5-dev with a memory leak (dev15 had some kind of leak, at least I've already seen it being oomed).
Could you please let us know which version you are running? cheers On Sat, Feb 2, 2013 at 6:01 PM, Lukas Tribus <[email protected]> wrote: > > Notice that having the HAproxy box swapping is a huge performance killer and > you absolutely do not want to do that, so apart from tuning/configuring the > OOM killer you should track the issue down and avoid memory depletion and > swapping in first place. > > > > ---------------------------------------- >> Date: Sat, 2 Feb 2013 12:34:03 +0000 >> Subject: Re: haproxy invoked oom-killer >> From: [email protected] >> To: [email protected] >> >> On 1 February 2013 21:57, Dusty Doris <[email protected]> wrote: >> > oom-killer just killed my haproxy instance. Anyone know if there is a way >> > to prioritize haproxy and have it get killed after something else? Or, any >> > tuning that might help. >> >> https://www.google.co.uk/search?q=linux+exclude+proces+from+oom-killer >> >> -- >> Jonathan Matthews // Oxford, London, UK >> http://www.jpluscplusm.com/contact.html >> >
