Percona XtraBackup moved to https://jira.percona.com/projects/PXB

Percona XtraBackup moved to https://jira.percona.com/projects/PXB 2.2.12

  1. Series 2.2
  2. 2.2.12

Milestone information

Project:
Percona XtraBackup moved to https://jira.percona.com/projects/PXB
Series:
2.2
Version:
2.2.12
Released:
 
Registrant:
Hrvoje Matijakovic
Release registered:
Active:
No. Drivers cannot target bugs and blueprints to this milestone.  

Download RDF metadata

Activities

Assigned to you:
No blueprints or bugs assigned to you.
Assignees:
7 Sergei Glushchenko, 3 Tomislav Plavcic
Blueprints:
No blueprints are targeted to this milestone.
Bugs:
10 Fix Released

Download files for this release

File Description Downloads

Release notes 

Changelog 

View the full changelog

Bugs Fixed¶
Percona XtraBackup would segfault during the prepare phase of certain FTS pages. Bug fixed #1460138.

Fixed compilation error due to missing dependency caused by the upstream bug #77226. Bug fixed #1461129.

Regression introduced by fixing a bug #1403237 in Percona XtraBackup 2.2.8 could cause xtrabackup to read a redo log from incorrect offset which would cause an assertion. Bug fixed #1464608.

Fixed uninitialized current_thd thread-local variable. This also completely fixes #1415191. Bug fixed #1467574.

After the release of Percona XtraBackup 2.2.11, innobackupex issues a FLUSH TABLE before running the FLUSH TABLES WITH READ LOCK. While it will help the backups in some situation, it also implies that the FLUSH TABLE will be written to the binary log. On MariaDB 10.0 with GTID enabled, when backup was taken on the slave, this altered the GTID of that slave and Percona XtraBackup didn’t see the correct GTID anymore. Bug fixed #1466446 (Julien Pivotto).

RPM compilation of Percona XtraBackup was still requiring bzr. Bug fixed #1466888 (Julien Pivotto).

Compiling Percona XtraBackup RPMs with XB_VERSION_EXTRA option would create an incorrect RPM version. Bug fixed #1467424 (Julien Pivotto).

Percona XtraBackup would complete successfully even when redo log wasn’t copied completely. This means that backup were considered successful even when they were corrupt. Bug fixed #1470847.

In rare cases when there are two or more tablespaces with the same ID in the data directory, xtrabackup picks up the first one by lexical order, which could lead to losing the correct table. Bug fixed #1475487.

Percona XtraBackup was missing revision_id in binaries. Bug fixed #1394174.

0 blueprints and 10 bugs targeted

Bug report Importance Assignee Status
1460138 #1460138 xtrabackup segfaults during --prepare of certain FTS pages 3 High Sergei Glushchenko  10 Fix Released
1461129 #1461129 Target sql_embedded should depend on GenDigestServerSource 3 High Sergei Glushchenko  10 Fix Released
1464608 #1464608 Failing assertion: byte_offset % OS_MIN_LOG_BLOCK_SIZE == 0, lsn_offset = 18446744073709551615 3 High Sergei Glushchenko  10 Fix Released
1467574 #1467574 xtrabackup should initialize current_thd 3 High Sergei Glushchenko  10 Fix Released
1466446 #1466446 "FLUSH TABLE" is written to the binary log 4 Medium Sergei Glushchenko  10 Fix Released
1466888 #1466888 RPM compilation still requires bzr 4 Medium Tomislav Plavcic  10 Fix Released
1467424 #1467424 RPM compilation with XB_VERSION_EXTRA creates a strange RPM version 4 Medium Tomislav Plavcic  10 Fix Released
1470847 #1470847 Percona Xtrabackup: Starting LSN is bigger than ending LSN 4 Medium Sergei Glushchenko  10 Fix Released
1475487 #1475487 xtrabackup handling of space id conflicts 4 Medium Sergei Glushchenko  10 Fix Released
1394174 #1394174 Empty "revision id" in PXB binaries 5 Low Tomislav Plavcic  10 Fix Released
This milestone contains Public information
Everyone can see this information.