apply log crashes - signal 11 (ib_warn_row_too_big)
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MySQL Server |
Unknown
|
Unknown
|
|||
Percona XtraBackup moved to https://jira.percona.com/projects/PXB |
Fix Released
|
High
|
Sergei Glushchenko | ||
2.2 |
Fix Released
|
High
|
Sergei Glushchenko | ||
2.3 |
Fix Released
|
High
|
Sergei Glushchenko |
Bug Description
Trying to innobackupex from a "5.5.38-35.2-log Percona Server (GPL), Release 35.2, Revision 674" master to a new slave.
apply-log fails with "19:04:21 UTC - xtrabackup got signal 11 ;"
Stack trace is as follow :
stack_bottom = 0 thread_stack 0x10000
xtrabackup(
xtrabackup(
/lib/x86_
xtrabackup(
xtrabackup(
xtrabackup(
xtrabackup(
xtrabackup() [0x6a35fb]
xtrabackup(
xtrabackup(
xtrabackup(
xtrabackup(
xtrabackup(
xtrabackup(
xtrabackup(
/lib/x86_
/lib/x86_
ib_warn_row_too_big may mean it's somehow related to https:/
Attached is the full log.
Relevant version numbers (on the new slave where apply log is run) :
ii libmysqlclient1
ii mysql-common 5.5.41-0+wheezy1 all MySQL database common files, e.g. /etc/mysql/my.cnf
ii percona-xtrabackup 2.2.8-5059-1.wheezy amd64 Open source backup tool for InnoDB and XtraDB
ii xtrabackup 2.2.8-5059-1.wheezy all Transitional package for percona-xtrabackup
Downgraded from (debian package)
xtrabackup version 2.2.8 based on MySQL server 5.6.22 Linux (x86_64) (revision id: )
to
xtrabackup version 2.2.3 based on MySQL server 5.6.17 Linux (x86_64) (revision id: )
And it did finish correctly.