trove/fix-mysql-replication-bf2b131994a5a772.yaml at 7b3483723a5fdfa56a8cc419ad77c8660ac87ad1 - trove - OpenDev: Free Software Needs Free Tools

openstack/trove

Doug Shelley 09a312ae3a Mysql GTID replication fails when data inserted

If you have a master and a slave configured and you insert
new data into the master, it will cause subsequent replica
create to fail.

The problem is that we weren't setting the gtid_purged variable
using the metadata in the xtrabackup_binlog_info file. The
Mysql GTID replication strategy was adjusted to account for this.

A release note has been added.

The replication scenario tests were enhanced to validate this
issue.

Note: this issue doesn't occur with MariaDB GTID replication
because it mechanism is different.

Scenario tests were run succesfully on Mysql, Percona and
MariaDB with this change in place.

Change-Id: I66c8b6278afa50ba14e4bb7888e3a25dc657a9e4
Closes-bug: 1563574

2016-04-21 16:05:24 +00:00

5 lines

195 B

YAML

Raw Blame History

 ---
 fixes:
   - Fixes an issue with a failure to establish a new replica for MySQL
     in some cases where a replica already exists and some data has
     been inserted into the master. Bug 1563574