Details
-
Bug
-
Status: Closed (View Workflow)
-
Critical
-
Resolution: Fixed
-
5.5.28
-
None
Description
We found a simple XA transaction that crashes MySQL 5.5 replication. This simple transaction merely inserts into InnoDB and TokuDB tables. The bug was caused by a flaw in the logging code exposed by the transaction’s use of two XA storage engines (TokuDB and InnoDB) and was fixed in the TokuDB 6.0.1 release.
Here are some details. Suppose that a database contains the following tables.
create table t1 (a int) engine=InnoDB
|
create table t2 (a int) engine=TokuDB
|
The following transaction
begin
|
insert into t1 values (1)
|
insert into t2 values (2)
|
commit
|
causes the replication slave to crash.
The crash occurs when mysqld tries to dereference a NULL pointer.
#4 0x000000000088e203 in MYSQL_BIN_LOG::log_and_order (this=0x14b8640, thd=0x7f7758000af0, xid=161, all=true, need_prepare_ordered=false, need_commit_ordered=true) at /home/mariadb-5.5.25/sql/log.cc:7491
|
7491 cache_mngr->using_xa= TRUE;
|
(gdb) p cache_mngr
|
$1 = (binlog_cache_mngr *) 0x0
|
the bug is fixed on lp:~prohaska7/5.5-xa-rpl-crash-fix
also, see mariadb-developers email thread.
Attachments
Activity
| Field | Original Value | New Value |
|---|---|---|
| Labels | Launchpad |
| Fix Version/s | Maria 5.5 [ 11303 ] | |
| Labels | Launchpad | Launchpad MariaDB_5.5 |
| Fix Version/s | 5.5.29 [ 11701 ] |
| Labels | Launchpad MariaDB_5.5 | Launchpad |
| Affects Version/s | 5.5.28 [ 11200 ] |
| Description |
We found a simple XA transaction that crashes MySQL 5.5 replication. This simple transaction merely inserts into InnoDB and TokuDB tables. The bug was caused by a flaw in the logging code exposed by the transaction’s use of two XA storage engines (TokuDB and InnoDB) and was fixed in the TokuDB 6.0.1 release. Here are some details. Suppose that a database contains the following tables. create table t1 (a int) engine=InnoDB create table t2 (a int) engine=TokuDB The following transaction begin insert into t1 values (1) insert into t2 values (2) commit causes the replication slave to crash. The crash occurs when mysqld tries to dereference a NULL pointer. #4 0x000000000088e203 in MYSQL_BIN_LOG::log_and_order (this=0x14b8640, thd=0x7f7758000af0, xid=161, all=true, need_prepare_ordered=false, need_commit_ordered=true) at /home/mariadb-5.5.25/sql/log.cc:7491 7491 cache_mngr->using_xa= TRUE; (gdb) p cache_mngr $1 = (binlog_cache_mngr *) 0x0 the bug is fixed on lp:~prohaska7/5.5-xa-rpl-crash-fix also, see mariadb developers email chain. |
We found a simple XA transaction that crashes MySQL 5.5 replication. This simple transaction merely inserts into InnoDB and TokuDB tables. The bug was caused by a flaw in the logging code exposed by the transaction’s use of two XA storage engines (TokuDB and InnoDB) and was fixed in the TokuDB 6.0.1 release. Here are some details. Suppose that a database contains the following tables. {noformat} create table t1 (a int) engine=InnoDB create table t2 (a int) engine=TokuDB {noformat} The following transaction {noformat} begin insert into t1 values (1) insert into t2 values (2) commit {noformat} causes the replication slave to crash. The crash occurs when mysqld tries to dereference a NULL pointer. {noformat} #4 0x000000000088e203 in MYSQL_BIN_LOG::log_and_order (this=0x14b8640, thd=0x7f7758000af0, xid=161, all=true, need_prepare_ordered=false, need_commit_ordered=true) at /home/mariadb-5.5.25/sql/log.cc:7491 7491 cache_mngr->using_xa= TRUE; (gdb) p cache_mngr $1 = (binlog_cache_mngr *) 0x0 {noformat} the bug is fixed on lp:~prohaska7/5.5-xa-rpl-crash-fix also, see mariadb-developers email thread. |
| Resolution | Cannot Reproduce [ 5 ] | |
| Status | Open [ 1 ] | Closed [ 6 ] |
| Resolution | Cannot Reproduce [ 5 ] | |
| Status | Closed [ 6 ] | Reopened [ 4 ] |
| Fix Version/s | 5.5.29 [ 12102 ] | |
| Fix Version/s | 5.5.28a [ 11701 ] |
| Status | Reopened [ 4 ] | In Progress [ 3 ] |
| Labels | Launchpad | Launchpad replication |
| Resolution | Fixed [ 1 ] | |
| Status | In Progress [ 3 ] | Closed [ 6 ] |
| Workflow | defaullt [ 21477 ] | MariaDB v2 [ 46470 ] |
| Workflow | MariaDB v2 [ 46470 ] | MariaDB v3 [ 67172 ] |
| Workflow | MariaDB v3 [ 67172 ] | MariaDB v4 [ 145080 ] |