Bug #26929 | DELETE statement takes too long | ||
---|---|---|---|
Submitted: | 7 Mar 2007 18:54 | Modified: | 8 Mar 2007 13:20 |
Reporter: | Mario Batista | Email Updates: | |
Status: | Not a Bug | Impact on me: | |
Category: | MySQL Server: InnoDB storage engine | Severity: | S5 (Performance) |
Version: | 5.0.27 | OS: | Linux (Redhat 9) |
Assigned to: | Heikki Tuuri | CPU Architecture: | Any |
[7 Mar 2007 18:54]
Mario Batista
[7 Mar 2007 19:18]
Valeriy Kravchuk
Thank you for a problem report. Please, send your entire my.cnf, SHOW INNODB STATUS results next time you will have a long running DELETEs, and the results of: uname -a free Linux commands.
[8 Mar 2007 12:33]
Mario Batista
[user@hostname user]$ uname -a Linux hostname 2.4.20-8smp #1 SMP Thu Mar 13 17:45:54 EST 2003 i686 i686 i386 GNU/Linux I will send the free command output when I check that a DELETE is taking too long. I uploaded to the FTP Server the file with the INNODB Monitor output when the problem happened and the my.cnf file. ftp://ftp.mysql.com/pub/mysql/upload/bub_id_26929_my.cnf ftp://ftp.mysql.com/pub/mysql/upload/bub_id_26929_mysqld.log.zip
[8 Mar 2007 13:20]
Heikki Tuuri
Mario, you should make innodb_buffer_pool bigger. You have 100 GB of data files, but only 100 MB of buffer pool! When you do a massive delete, the row lock table of InnoDB may exhaust the buffer pool. Regards, Heikki