300 seconds is 5 minutes, while this whole thing happened probably under a
minute. I'm looking for possible causes, not workarounds :-)
On Fri, Nov 26, 2010 at 8:57 PM, Prabhat Kumar <aim.prabhat@stripped>wrote:
> to avoid this change ur "wait_timeout" value to 300 Secs or less, along
> with this you can also write a script to kill those process (mysql process)
> which are in sleep mode for more than certain time..
> hope this will helpful..
> On Wed, Nov 24, 2010 at 6:41 PM, Johan De Meersman <vegivamp@stripped
> > On Wed, Nov 24, 2010 at 1:13 PM, Nigel Wood <nwood@stripped> wrote:
> > > Quick thought: what is your idle timeout set to on the MySQL server?
> > > Could you have configured it to reap these idle connections?
> > >
> > I could, probably, but the applications are generally well-behaved, and
> > it's
> > not a recurring problem. I hope. I'm more interested in the cause, atm.
> > On Wed, Nov 24, 2010 at 1:58 PM, John Daisley <
> > >wrote:
> > > Seen this a lot with poorly written web apps which open connections but
> > > dont
> > > close them when finished. Try setting wait_timeout and/or
> > > interactive_timeout to close unused connections.
> > >
> > Well, yes, but as far as we're aware nothing new has been deployed - this
> > setup is several years old. I suppose it's possible that one of those
> > of bugs is hiding somewhere in a forgotten corner of code, but given that
> > we're running Drupal and Wordpress, I'd be surprised at something like
> > remaining unnoticed for so long.
> > --
> > Bier met grenadyn
> > Is als mosterd by den wyn
> > Sy die't drinkt, is eene kwezel
> > Hy die't drinkt, is ras een ezel
> Best Regards,
> Prabhat Kumar
> MySQL DBA
> My Blog: http://adminlinux.blogspot.com
> My LinkedIn: http://www.linkedin.com/in/profileprabhat
Bier met grenadyn
Is als mosterd by den wyn
Sy die't drinkt, is eene kwezel
Hy die't drinkt, is ras een ezel