From: Rich Prohaska
Date: June 4 2012 5:23pm
Subject: crash in slave replication with XA transaction
List-Archive: http://lists.mysql.com/internals/38518
Message-Id: <CAB3YYRXjaqd-XRzZMABKowgZy14SciVBUeJgccW-YqUzaVdnVg@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Hello,

We are running MySQL 5.5.21 with both InnoDB and TokuDB as XA storage
engines. =A0When one runs a transaction that inserts into an InnoDB
table and a TokuDB table, the commit crashes the replication slave at
log.cc line 6602 because cache_mngr =3D=3D NULL. =A0We found a pattern in
various log functions in log.cc that calls binlog_setup_trx_data to
initialize the txn state.

This change fixes our immediate problem.

$ diff log.cc.orig log.cc
6595a6596,6597
> =A0 if (thd_get_ha_data(thd, binlog_hton) =3D=3D NULL)
> =A0 =A0 thd->binlog_setup_trx_data();

Is this a correct fix? =A0If so, are there other places that need a
similar change?

Thanks
Rich Prohaska


The transaction is:
create table t1 (a int primary key) engine=3Dinnodb;
create table t2 (a int primary key) engine=3Dtokudb;
set autocommit=3D0;
insert into t1 values (1);
insert into t2 values (2);
commit;

the slave crashes while handling the commit binlog entry.