ourdelta-developers team mailing list archive

[MARK CALLAGHAN <mdcallag@xxxxxxxxx>]

On Tue, Mar 17, 2009 at 12:00 PM, MARK CALLAGHAN <mdcallag@xxxxxxxxx> wrote:
> On Tue, Mar 17, 2009 at 11:43 AM, Neil Katin <launchpad@xxxxxxxxxxx> wrote:
>> Public bug reported:
>>
>>
>> We recently upgraded to the ourdelta patch set (Centos5.2, x86_64, 5.0.67.d7-44.el5_2).  We were running the provenscaling version mysql).
>>
>> Ever since the upgrade we seem to be having a memory leak in mysqld; the
>> executable is growing by about 3gb a day.  Here's an rrd graph of our
>> memory usage; you can see the "green" (apps) portion of memory growing
>> right after we performed the upgrade (at the end of week 8).
>>
>> http://www.sonic.net/~nk31/memory-month.png
>>
>> The application didn't change at that time; we are running the exact
>> same SQL queries and workload before and after the update.
>>
>> I realize that I don't have enough info to allow you to fix any problems
>> in this but report (but if you can think of something we could measure
>> for you, I will).  But I did want to see if anyone else has seen any
>> leakage issues in this version of mysqld.
>>
>> Thanks.
>>
>> ** Affects: ourdelta
>>     Importance: Undecided
>>         Status: New
>>
>> --
>> Memory leak in mysqld?
>> https://bugs.launchpad.net/bugs/344447
>> You received this bug notification because you are a member of OurDelta-
>> developers, which is the registrant for OurDelta.
>>
>> Status in OurDelta - Builds for MySQL: New
>>
>> Bug description:
>>
>> We recently upgraded to the ourdelta patch set (Centos5.2, x86_64, 5.0.67.d7-44.el5_2).  We were running the provenscaling version mysql).
>>
>> Ever since the upgrade we seem to be having a memory leak in mysqld; the executable is growing by about 3gb a day.  Here's an rrd graph of our memory usage; you can see the "green" (apps) portion of memory growing right after we performed the upgrade (at the end of week 8).
>>
>> http://www.sonic.net/~nk31/memory-month.png
>>
>> The application didn't change at that time; we are running the exact same SQL queries and workload before and after the update.
>>
>> I realize that I don't have enough info to allow you to fix any problems in this but report (but if you can think of something we could measure for you, I will).  But I did want to see if anyone else has seen any leakage issues in this version of mysqld.
>>
>> Thanks.
>>
>> _______________________________________________
>> Mailing list: https://launchpad.net/~ourdelta-developers
>> Post to     : ourdelta-developers@xxxxxxxxxxxxxxxxxxx
>> Unsubscribe : https://launchpad.net/~ourdelta-developers
>> More help   : https://help.launchpad.net/ListHelp
>>
>
> Arjen -- can SHOW CLIENT_STATISTICS data collection be disabled? If
> so, then that should be done to see if it makes the leak go away.

I just looked at my notes. The bug that I fixed (and the fix is in the
big Google v3 patch) occurs when SHOW CLIENT_STATISTICS data
collection is done and the server is run without --skip-name-resolve.

>
> --
> Mark Callaghan
> mdcallag@xxxxxxxxx
>



-- 
Mark Callaghan
mdcallag@xxxxxxxxx