With a quick googling LP: #1401133 might be related: https://bugs.launchpad.net/percona-xtradb-cluster/+bug/1401133 > There are 2 parts to this bug report: > > 1. Deadlock is triggered by the LOCK BINLOG FOR BACKUP statement > executed by XtraBackup > 2. The XtraBackup connection is closed due to the above error while > holding a backup (TABLE) lock. Which results in a heap corruption and a > server crash, possibly some time later. > > I believe #2 has been reported and fixed in PS 5.6.24-72.2 with > https://github.com/percona/percona-server/pull/26 > > Which means the latest PXC release 5.6.24-25.11 should not crash when > backup locks are used by XtraBackup if my > assumption is correct, but XtraBackup may still fail with an error due > to #1. > > #1 (as in, a deadlock with LOCK BINLOG FOR BACKUP) looks like a > PXC-specific issue, but so far I’ve been unable to reproduce it > neither with PXC 5.6.22-25.8 nor with PXC 5.6.24-25.11.
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1646795 Title: mysqld got signal 11 during innobackupex To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/percona-xtradb-cluster-5.6/+bug/1646795/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
