LVS
lvs-users
Google
 
Web LinuxVirtualServer.org

Re: [lvs-users] memory usage of ldirectord

To: "LinuxVirtualServer.org users mailing list." <lvs-users@xxxxxxxxxxxxxxxxxxxxxx>
Subject: Re: [lvs-users] memory usage of ldirectord
From: Steve Wray <steve.wray@xxxxxxxxx>
Date: Tue, 04 Dec 2007 08:00:26 +1300
Simon Horman wrote:
> On Mon, Dec 03, 2007 at 01:53:09PM +1300, Steve Wray wrote:
>> Joseph Mack NA3T wrote:
>>> On Mon, 3 Dec 2007, Steve Wray wrote:
>>>
>>>> I'm currently seeing the ldirectord process using 171M of RAM (as
>>>> displayed by top).
>>> I don;t know if this is your problem but...
>>>
>>> I believe there was a memory leak for which Ratz provided a 
>>> patch in about Apr this year. AFAIK, this patch is in some 
>>> branch of ldirectord (I don't know whether it's been 
>>> released, you could look at the release notes for the 
>>> version you have).
>> Might this be related:
>>
>> http://osdir.com/ml/linux.highavailability.ultramonkey/2006-04/msg00011.html
>>
>> Debian appears to use something other than IO::Socket::INET
> 
> Hi All,
> 
> 171M does sound rather ecessive to me. And its probably a memory leak
> somewhere. The trick is that it probably lies in an underlying library
> and only manifest with certain combinations of perl libraries installed
> and perhaps with only specific configurations.
> 
> Ok, that was just waffly not very useful information.
> If the problem is readily reproducable it would be tremendously
> useful if you could try and narrow down the cause of the problem.
> The SSL code has exhibited memory leaks in the past, so that
> might be a good place to start.

The server in question has been up for nearly a month when this memory 
usage was noted.

That director node has been shut down thereby invoking a failover to the 
previously passive director and the director with the memory issue rebooted.

I'll keep a close eye on memory usage.



> As for changes to ldirectord. It is currently living in the linux-ha
> mecurial tree. All changes should be in the dev tree, which you
> can see here:
> 
> http://hg.linux-ha.org/dev/log/b263292dc60f/ldirectord/ldirectord.in
> 
> Up until last year that tree was in CVS, the historical changes
> can be viewed at:
> 
> http://cvs.linux-ha.org/viewcvs/viewcvs.cgi/linux-ha/ldirectord/ldirectord.in?rev=1.42&view=log
> 
> And before that
> 
> http://cvs.linux-ha.org/viewcvs/viewcvs.cgi/linux-ha/ldirectord/Attic/ldirectord?rev=1.144&view=log
> 
> There is/are other branches of the linux-ha tree, such as the old 1.2
> stable branch, and various staging trees. And ldirectord exists in all
> of these trees. However, as I mentioned above most/all changes go
> through the main tree.
> 
> 
> Lastly, if you want to file a Debian bug for this problem thats fine.
> It might get some more eyes on the problem. I deal with both upstream
> and Debian maintenance of ldirectord, so I do check the Debian bug
> tracker and close bugs if/when they get solved.
> 



<Prev in Thread] Current Thread [Next in Thread>