[MDEV-30666] Different GTID for the same binlog File + Position (xtrabackup_binlog_info vs binlog_gtid_pos) Created: 2023-02-17 Updated: 2023-04-03 Resolved: 2023-03-17 |
|
| Status: | Closed |
| Project: | MariaDB Server |
| Component/s: | Galera, mariabackup |
| Affects Version/s: | 10.5.12 |
| Fix Version/s: | N/A |
| Type: | Bug | Priority: | Critical |
| Reporter: | Kwangbock Lee | Assignee: | Julius Goryavsky |
| Resolution: | Incomplete | Votes: | 0 |
| Labels: | None | ||
| Issue Links: |
|
||||||||
| Description |
|
Customer is trying to set up replication from the backup. When configuring replication, they used GTID from xtrabackup_binlog_info but it failed when starting slave. Then they checked the GTID by BINLOG_GTID_POS function, it showed different value of GTID and replication works with this GTID. I've quickly ran some tests here and I could easily see GTID difference.
And I also ran the same test on 10.5.17 but it showed all same GTID.
|
| Comments |
| Comment by Julius Goryavsky [ 2023-03-17 ] |
|
Closed as resolved in 10.5.17, presumably a duplicate of |