[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:
Relates
relates to MDEV-21037 mariabackup does not detect multi-sou... Closed

 Description   

Customer is trying to set up replication from the backup.
They are using Mariabackup 10.5.12 along with MariaDB cluster 10.5.12.

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.

[root@clusterS-3 backup]# cat xtrabackup_binlog_info 
ON.000005	387	10-1000-7624298,50-5000-3,1001-1000-2
 
 
MariaDB [(none)]> select binlog_gtid_pos('ON.000005', 387);
+-----------------------------------+
| binlog_gtid_pos('ON.000005', 387) |
+-----------------------------------+
| 10-1000-7624302,50-5000-3         |
+-----------------------------------+
1 row in set (0.000 sec)
 
MariaDB [(none)]> show variables like '%gtid%';
+-------------------------+---------------------------------------+
| Variable_name           | Value                                 |
+-------------------------+---------------------------------------+
| gtid_binlog_pos         | 10-1000-7624302,50-5000-3             |
| gtid_binlog_state       | 10-1000-7624302,50-5000-3             |
| gtid_cleanup_batch_size | 64                                    |
| gtid_current_pos        | 10-1000-7624298,50-5000-3,1001-1000-2 |
| gtid_domain_id          | 5003                                  |
| gtid_ignore_duplicates  | ON                                    |
| gtid_pos_auto_engines   |                                       |
| gtid_seq_no             | 0                                     |
| gtid_slave_pos          | 10-1000-7624298,1001-1000-2           |
| gtid_strict_mode        | OFF                                   |
| last_gtid               |                                       |
| wsrep_gtid_domain_id    | 50                                    |
| wsrep_gtid_mode         | ON                                    |
| wsrep_gtid_seq_no       | 0                                     |
+-------------------------+---------------------------------------+
14 rows in set (0.001 sec)

And I also ran the same test on 10.5.17 but it showed all same GTID.

[root@clusterP-2 b2]# cat xtrabackup_binlog_info 
ON.000011	387	10-1000-7624298,50-5000-2
 
MariaDB [(none)]> select binlog_gtid_pos('ON.000011', 387);
+-----------------------------------+
| binlog_gtid_pos('ON.000011', 387) |
+-----------------------------------+
| 10-1000-7624298,50-5000-2         |
+-----------------------------------+
1 row in set (0.001 sec)



 Comments   
Comment by Julius Goryavsky [ 2023-03-17 ]

Closed as resolved in 10.5.17, presumably a duplicate of MDEV-21037

Generated at Thu Feb 08 10:17:59 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.