maria-developers team mailing list archive

[Sergei Golubchik <serg@xxxxxxxxxxxx>]

Hi, jhx1008!

On May 02, Sergei Golubchik wrote:
> Hi, jhx1008!
> 
> This also looks very much like a bug to me.
> Could you please report it at mariadb.org/jira ?

Thanks!

Just for the reference - in case anyone on the list is following,
it's https://mariadb.atlassian.net/browse/MDEV-4470

> On May 02, jhx1008 wrote:
> > hello
> > I have another problem witch seems like a bug(Server version: 5.5.5-10.0.2-MariaDB-log MariaDB Server).
> > the problem is about the replication for the xa transactions when the master crashed and then restarted.
> > I know when we do a transaction, the queries will be stored in the binlog cache, after commit, flush the binlog cache into the binlog file, any normal un-committed transactions will be rollbacked when the server crashed then restarted, but the prepared xa transactions are not. 
> > Prepared xa transactions can be recovered use the command 'xa recover',  then committed use 'xa commit xid', but the binlog cache is empty when the master restart, so if we do the 'xa commit xid', nothing to be recorded into the binlog files, the replication will be broken.
> > test:
> > master
Regards,
Sergei