[rt-users] Bad query?

Matthew Watson mwatson at netspace.net.au
Thu Sep 19 18:38:06 EDT 2002


 I used to get this too, it happens when someone does a 
search for tickets, limiting on the requestor, thats a slow
query, especially since it doesn't seem to be indexable 
(someone please send me in the index if I'm wrong). And it
gets REALLY bad when you try and limit 2 requestors..

 I got around that by making it so you cannot limit more than
one requestor, not great, but better than bringing the db to a
halt.
 
 The reason the db is grinding to a halt is due to mysql's default
behaviour of table level locking, as was suggested innodb tables
should fix this, as should moving to a db that has more advanced
locking that mysql :)

Mat.


> -----Original Message-----
> From: rt-users-admin at lists.fsck.com
> [mailto:rt-users-admin at lists.fsck.com]On Behalf Of Jon Hittner
> Sent: Friday, 20 September 2002 8:26 AM
> To: Mark E. Dawson, Jr.; rt-users at lists.fsck.com
> Subject: Re: [rt-users] Bad query?
> 
> 
>    There where a few other procs, all small select statements and update 
> statements, and all in a "locked" state.  I don't want to have to 
> upgrade to 
> Oracle for a problem that only happens every few weeks.  For the 
> most part 
> the system is very fast.   If there any way to isolate this query 
> and remove 
> the ability for rt to do perform it?
> 
> Jon
> 
> On Thursday 19 September 2002 06:12 pm, Mark E. Dawson, Jr. wrote:
> > > Hi,
> > >    Im running rt 2.0.9.   About once every 2 weeks
> > > the system seems to lock up.   When I do a show full
> > > processlist I see the query that is causing the
> > > problem:
> >
> > I'm more interested in what else showed up in the
> > show full proc listing.  Was this the *only* entry,
> > or were there others?
> >
> > I used to have a heck of a problem with MySQL's
> > default locking granularity (which is table-level)
> > with a number of different apps.  Readers and writers
> > blocking each other at that coarse a granularity
> > will kill you.
> >
> > Try using InnoDB or BDB tables instead within the
> > database, if you in fact find this to be your issue.
> > Otherwise, migrate to another database like Oracle.
> >
> > __________________________________________________
> > Do you Yahoo!?
> > New DSL Internet Access from SBC & Yahoo!
> > http://sbc.yahoo.com
> 
> _______________________________________________
> rt-users mailing list
> rt-users at lists.fsck.com
> http://lists.fsck.com/mailman/listinfo/rt-users
> 
> Have you read the FAQ? The RT FAQ Manager lives at http://fsck.com/rtfm
> ---
> Incoming mail is certified Virus Free.
> Checked by AVG anti-virus system (http://www.grisoft.com).
> Version: 6.0.389 / Virus Database: 220 - Release Date: 16/09/2002
> 
---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.389 / Virus Database: 220 - Release Date: 16/09/2002




More information about the rt-users mailing list