ourdelta-developers team mailing list archive

[Arjen Lentz <arjen@xxxxxxxxxxxxx>]

Hi Mark, Neil

On 18/03/2009, at 5:00 AM, MARK CALLAGHAN wrote:

> On Tue, Mar 17, 2009 at 11:43 AM, Neil Katin <launchpad@xxxxxxxxxxx>  
> wrote:
>> We recently upgraded to the ourdelta patch set (Centos5.2, x86_64,  
>> 5.0.67.d7-44.el5_2).
>> Ever since the upgrade we seem to be having a memory leak in mysqld
>
> 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.


Not in the d7 patchset. We added one switch for all the _statistics  
info later so people only have the contention/overhead when the info  
is needed.

So Neil, if you can bear with us, we're prepping the 5.0.77 build  
right now with updated/new patches. If that version still has the  
problem, then at least we'll be able to toggle the patch that we  
suspect might be causing the problem, allowing you to catch the issue.  
Oki?


Cheers,
Arjen.
-- 
Arjen Lentz, Director @ Open Query (http://openquery.com)
Affordable Training and ProActive Support for MySQL & related  
technologies

My blog is at http://arjen-lentz.livejournal.com
OurDelta: free enhanced builds for MySQL @ http://ourdelta.org

-- 
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.