June 19, 2013

Post: Percona XtraDB Cluster 5.5.30-23.7.4 for MySQL now available

…table when appending exclusive key for cascading delete operation. Bug fixed #1089490 (Seppo Jaakola). …Alex Yurchenko). If variable innodb_thread_concurrency has been defined to throttle InnoDB access, and work load… did our best to eliminate bugs and problems, but this is a software, so bugs …

Post: Heikki Tuuri Innodb answers - Part I

… you delete a lot of scattered rows you may not see a “free space” in Innodb tablespace to grow significantly. Q6: Does Innodb… of little known aspects of Innodb operations while I see it causing problems every so often. Q16: How Innodb decided how many pages… often solves your thrashing problem. PZ: Values 1,2 may solve your thrashing problem but also will limit innodb to be able to…

Post: My Innodb Feature wishes

delete. For Insert operation Innodb uses nice tecnique called Insert Buffer which speeds up inserts for non-unique indexes a lot. However deletes… it is so bad I will list it. Basically Innodb has problems scaling both with large number of active threads and with… it is too bad even with 4 concurrent queries). The problem seems to be at least partially due to global mutexes…

Post: InnoDB Full-text Search in MySQL 5.6 (part 1)

… explicit FTS_DOC_ID column, however, MySQL apparently has no problem with either of the following statements: mysql> insert into dir… two, delete some data, and see what happens: mysql> set global innodb_ft_aux_table=’test/dir_test_innodb‘; mysql> set global innodb_optimize…) mysql> delete from dir_test_innodb LIMIT 200000; Query OK, 200000 rows affected (8.65 sec) mysql> optimize table dir_test_innodb; +———————-+———-+———-+———-+ | Table…

Post: A quest for the full InnoDB status

… with one simple command — SHOW ENGINE InnoDB STATUS. On most occasions it works beautifully. The problems appear when you have a large… all the files that were deleted. garfield ~ # cd /proc/11886/fd garfield fd # ls -l | grep deleted lrwx—— 1 root root 64… InnoDB status is. You can also help yourself with lsof tool available for many platforms: garfield fd # lsof -c mysqld | grep deleted

Post: InnoDB's gap locks

…. They only occur if you do UPDATE or DELETE or SELECT FOR UPDATE. InnoDB provides REPEATABLE READ for read-only SELECT, but…? Is possible to detect those gap locks using SHOW ENGINE INNODB STATUS: —TRANSACTION 72C, ACTIVE 755 sec 4 lock struct(s… phantom reads (non repeatable reads) so in order to prevent problems with the replication you should change the binary log format…

Post: INSERT INTO ... SELECT Performance with Innodb tables.

… extra locks. If you use this aproach make sure to delete file after it is loaded back (it has to be… cause the problems. To complete this article I should show how wait caused by this statement will look in SHOW INNODB STATUS: —TRANSACTION 0 42304626, ACTIVE 14 sec, process no 29895, OS thread id 2894768 updating or deleting mysql tables…

Post: Recovering Innodb table Corruption

… Running in innodb_force_recovery mode Innodb becomes read only for data operations and so you can’t insert or delete any data (though you can create or drop Innodb tables): mysql> optimize table test; +———–+———-+———-+———————————-+ | Table… same time I saw some data could be selected. The problem is there is some buffering taking place and as MySQL…

Post: SHOW INNODB STATUS walk through

… thousands of OS waits per second it may be the problem. The other way to look at it is context switch… thread is not runniing inside innodb kernel status could be “waiting in InnoDB queue” or “sleeping before joining InnoDB queue”. Latest one is… inside InnoDB Main thread process no. 10099, id 88021936, state: waiting for server activity Number of rows inserted 143, updated 3000041, deleted

Post: Innodb undo segment size and transaction isolation

… for execution, this however only applies to read transactions while problem with undo space growth exists for read only transactions as… record in undo space so row can be deleted on rollback, update and delete however need to put the old row version… queries will cause problems in this case anyway, even if you set transaction isolation to lowest READ-UNCOMMITTED level Innodb will not…