lp:~gl-az/percona-xtrabackup/2.1-bug1190610

Created by George Ormond Lorch III on 2013-06-18 and last modified on 2013-06-18
Get this branch:
bzr branch lp:~gl-az/percona-xtrabackup/2.1-bug1190610
Only George Ormond Lorch III can upload to this branch. If you are George Ormond Lorch III please log in for upload directions.

Branch merges

Related bugs

Related blueprints

Recent revisions

611. By George Ormond Lorch III on 2013-06-18

Fix for bug 1190610 : Decryption fails at a later stage.

xbcrypt_read_chunk was relying on blocking/full I/O even though it didn't
specify MY_FULL_IO during the bulk data read. Added ability to pass
desired flags down through read mechanism callback so that header reads
can fail on EOF and bulk data can block until data is available.

610. By Alexey Kopytov on 2013-06-14

Bug #1190716: innobackupex --safe-slave-backup hangs when used on
              master

The problem was in uninitialized value usage in wait_for_safe_slave()
when the server is not a replication slave, i.e. when no values in
$con->{slave_status} are defined.

Fixed by moving the check for $con->{slave_status}->{Slave_SQL_Running}
after the check for $host_is_slave and checking if Slave_SQL_Running is
defined when setting $host_is_slave for extra-safety.

608. By Alexey Kopytov on 2013-05-23

Merged trunk.

606. By Alexey Kopytov on 2013-05-22

Bug #1182698: XtraBackup 2.1.2 Hangs on SST

The problem was in the keepalives process ignoring SIGINT, so
innobackupex got stuck in stop_keepalives() waiting for the child
process to exit.

Disable keepalives completely for the server connection. Instead set
wait_timeout unconditionally, i.e. even if keepalives are disabled.

604. By <email address hidden> on 2013-05-17

Merge lp:~hrvojem/percona-xtrabackup/rn-2.1.2

603. By Alexey Kopytov on 2013-05-16

Empty merge from 2.0.

Branch metadata

Branch format:
Branch format 7
Repository format:
Bazaar repository format 2a (needs bzr 1.16 or later)
Stacked on:
lp:percona-xtrabackup/2.1
This branch contains Public information 
Everyone can see this information.