extra GTID in GTID_PURGED on master

Bug #1248231 reported by Teemu Ollakka on 2013-11-05
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MySQL patches by Codership
Status tracked in 5.6
5.6
Undecided
Unassigned
Percona XtraDB Cluster moved to https://jira.percona.com/projects/PXC
Status tracked in 5.6
5.5
Invalid
Undecided
Unassigned
5.6
New
Undecided
Unassigned

Bug Description

After couple of runs with attached randgen grammar, node with wsrep enabled and gtid_mode=ON shows extra GTID in mysqldump GTID_PURGED:

SET @@GLOBAL.GTID_PURGED='29a0f816-b9d9-ee1c-70f5-252d7899b3c0:1-23998,
d537295c-4626-11e3-8c4e-b499ba553e70:1';

Config:

binlog_format=ROW
log_bin=mysql-bin
log_slave_updates=1
gtid_mode=ON
enforce_gtid_consistency

Teemu Ollakka (teemu-ollakka) wrote :

@Teemu, @Phillip,

Is this still repeatable.

Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PXC-1508

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers