lp://staging/~sergei.glushchenko/percona-xtrabackup/2.2-xb-bug1368846

Branch merges

Propose for merging

No branches dependent on this one.

Related source package recipes

No recipes using this branch. (?)

Create packaging recipe

Related snap packages

Related bugs

Bug #1368846: xtrabackup Assertion failure with Apply log process

Medium

Fix Released

Link a bug report

Related blueprints

5054. By Sergei Glushchenko on 2015-01-28

Bug 1368846: xtrabackup Assertion failure with Apply log process

Looking at the stack trace I see pending IO complete operations
which led ibuf_merge after page_cleaner has stopped. We should not
stop page_cleaner if there are pending read IOs.

5053. By Alexey Kopytov on 2014-12-10

Merged lp:~percona-core/percona-xtrabackup/release-2.2.7.

5052. By Alexey Kopytov on 2014-12-10

Empty merge from 2.1.

5051. By Alexey Kopytov on 2014-12-10

Merged lp:~sergei.glushchenko/percona-xtrabackup/2.2-xb-bug1363234.

5050. By Alexey Kopytov on 2014-12-10

Merged lp:~hrvojem/percona-xtrabackup/rn-2.2.7-2.2.

5049. By Alexey Kopytov on 2014-12-03

Merged lp:~sergei.glushchenko/percona-xtrabackup/2.2-xb-bug1391041.

5048. By Sergei Glushchenko on 2014-11-30

Bug 1391216: Xtrabackup 2.2.5 fails with non-default innodb_log_block_size in 5.6.19

Port fix for Percona Server bug 1114612 to XtraBackup.

Original commit message:

Fix bug 1114612 (Failing assertion: n % srv_log_block_size == 0 in
file os0file.c line 4269).

The assertion happens because InnoDB I/O and AIO routines assume that
all I/O is done in log block size blocks. This works OK with the
default log block size of 512, but is likely to assert with large
innodb_log_block_size values.

Fix by asserting that all I/O is done in the minimum allowed log block
size blocks, that is, 512 bytes.

5047. By Alexey Kopytov on 2014-11-28

Bug #1366065: Exporting tables is inefficient when backup contains a
              large (and unrelated) change buffer

Merged a patch contributed by Davi Arnaut:

XtraBackup is quite efficient at exporting tables from a backup when it
contains a large change buffer (aka insert buffer) that is mostly
composed of changes to tables other than the tables being exported.

The problem arises from the need to merge change buffer entries when
exporting tables. In order to accomplish this, XtraBackup relies on a
normal InnoDB shutdown that merges pending change buffer entries. The
problem is that this background merging does random dives into the
change buffer index (see ibuf_merge_pages), making the process rather
inefficient if most of the entries in the change buffer are for tables
that are not even part of the backup.

An easy solution is to simply discard all change buffer entries for an
inexistent (deleted) tablespace once the first entry for such tablespace
is found. Ideally and if possible, make export akin to FLUSH TABLES FOR
EXPORT and do a fast shutdown.

5046. By Alexey Kopytov on 2014-11-21

Empty merge from 2.1.

5045. By Alexey Kopytov on 2014-11-21

Merged lp:~akopytov/percona-xtrabackup/bug1394632-2.2.