a mysqldump causes all other queries to be queued super slow. Any
am 22.03.2010 19:08:50 von Andres Salazar
Hello,
Everytime i run a mysqldump (mysql-server-5.0.77) all the other
legitimate queries that are ocurring at that time pretty much sleep
and build up in the processlist untill I either stop the dump or wait
for it finish. The moment i do either one i can have about 8-15
queries waiting they all free up immediately.
What could be causing this? I know there might be many factors
involved but Id like to get some clues as to where to look.
Thanks
Andres
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/mysql?unsub=gcdmg-mysql-2@m.gmane.org
Re: a mysqldump causes all other queries to be queued super slow. Any clue what is going on?
am 22.03.2010 19:55:50 von mussatto
On Mon, March 22, 2010 11:08, Andres Salazar wrote:
> Hello,
>
> Everytime i run a mysqldump (mysql-server-5.0.77) all the other
> legitimate queries that are ocurring at that time pretty much sleep
> and build up in the processlist untill I either stop the dump or wait
> for it finish. The moment i do either one i can have about 8-15
> queries waiting they all free up immediately.
>
> What could be causing this? I know there might be many factors
> involved but Id like to get some clues as to where to look.
>
> Thanks
>
> Andres
>
First, what are the table types?
Did you set --lock-tables? This will lock the tables within a database
That could cause the behavior you are seeing. I get a similar result when
I do a repair table For transaction enabled table types try
--single-transaction since it avoids read locks (according to the man
pages.
------
William R. Mussatto
Systems Engineer
http://www.csz.com
909-920-9154
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/mysql?unsub=gcdmg-mysql-2@m.gmane.org
Re: a mysqldump causes all other queries to be queued super slow. Any
am 22.03.2010 20:11:42 von Andres Salazar
Hello,
On Mon, Mar 22, 2010 at 12:55 PM, Wm Mussatto wrote:
>>
> First, what are the table types?
MyISAM
> Did you set --lock-tables? =A0No
> That could cause the behavior you are seeing. =A0I get a similar result w=
hen
> I do a repair table =A0 For transaction enabled table types try
> --single-transaction since it avoids read locks (according to the man
> pages.
Thats great however ... this type of result was not being exibited
some months ago.. i know the database was grown . It has also happened
that some big queries done against it also cause the same issue. I
think this is a bigger issue then just a mysqldump.
Iam trying to figure out why or where should i look.
Andres
>
> ------
> William R. Mussatto
> Systems Engineer
> http://www.csz.com
> 909-920-9154
>
>
> --
> MySQL General Mailing List
> For list archives: http://lists.mysql.com/mysql
> To unsubscribe: =A0 =A0http://lists.mysql.com/mysql?unsub=3Dndrsslzr80@gm=
ail.com
>
>
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/mysql?unsub=3Dgcdmg-mysql-2@m.gmane.o rg