Create table fails with unclear warning message

Bug #798006 reported by Vadim Tkachenko
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MySQL patches by Codership
Fix Released
High
Alex Yurchenko
0.8
Fix Released
High
Alex Yurchenko
Trunk
Fix Committed
High
Alex Yurchenko

Bug Description

I am using codership-mysql/0.8 with innodb_plugin
and trying to create sysbench multi-tables in parallel , using next command:

sysbench --test=tests/db/parallel_prepare.lua --oltp-tables-count=16 --num-threads=16 --oltp-table-size=25000000 --mysql-socket=/var/lib/mysql/mysql.sock run

In result error.log filled with messages:

110615 20:47:22 [Warning] WSREP: TO isolation failed for: 3, sql: CREATE TABLE sbtest10 (
id INTEGER UNSIGNED NOT NULL AUTO_INCREMENT,
k INTEGER UNSIGNED DEFAULT '0' NOT NULL,
c CHAR(120) DEFAULT '' NOT NULL,
pad CHAR(60) DEFAULT '' NOT NULL,
PRIMARY KEY (id)
) /*! ENGINE = innodb MAX_ROWS = 1000000 */
110615 20:47:22 [Warning] WSREP: TO isolation failed for: 3, sql: CREATE TABLE sbtest1 (
id INTEGER UNSIGNED NOT NULL AUTO_INCREMENT,
k INTEGER UNSIGNED DEFAULT '0' NOT NULL,
c CHAR(120) DEFAULT '' NOT NULL,
pad CHAR(60) DEFAULT '' NOT NULL,
PRIMARY KEY (id)
) /*! ENGINE = innodb MAX_ROWS = 1000000 */

and in fact only one table "sbtest2" created after this command, so it seems other tables failed.

Maybe there is reason why, but Warning message "[Warning] WSREP: TO isolation failed for: 3,"
does not provide much information.

Revision history for this message
Teemu Ollakka (teemu-ollakka) wrote :

The reason for message

110615 20:47:22 [Warning] WSREP: TO isolation failed for: 3, sql: CREATE ...

is that certification for statement run in server level total order isolation fails. This is essentially provider issue, reported separately here: https://bugs.launchpad.net/galera/+bug/798202.

Keeping this bug open for error message improvements.

Changed in codership-mysql:
milestone: none → 0.8.1
Changed in codership-mysql:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.