Details
-
New Feature
-
Status: Open (View Workflow)
-
Minor
-
Resolution: Unresolved
-
None
Description
At present semi-sync event log messages don't have any gtid info whereas async ones have it. IMO semi-sync messages should also have the gtid info.
ex:
2025-06-27 19:44:29 21 [Note] Start binlog_dump to slave_server(102), pos(binny1.000001, 1824), using_gtid(1), gtid('0-101-9')
|
2025-06-27 19:44:29 21 [Note] Start semi-sync binlog_dump to slave (server_id: 102), pos(./binny1.000001, 285)
|
2025-06-27 19:44:29 10 [Note] Semi-sync replication switched ON with slave (server_id: 102) at (binny1.000001, 2159)
|
2025-06-27 19:44:39 22 [Note] Start binlog_dump to slave_server(103), pos(binny1.000001, 1824), using_gtid(1), gtid('0-101-9')
|
2025-06-27 19:44:39 22 [Note] Start semi-sync binlog_dump to slave (server_id: 103), pos(./binny1.000001, 285)
|
2025-06-27 19:47:11 17 [Warning] Timeout waiting for reply of binlog (file: binny1.000001, pos: 2492), semi-sync up to file binny1.000001, position 2327.
|
Repro
mtr rpl.rpl_semi_sync
Attachments
Issue Links
- relates to
-
MDEV-21322 report slave progress to the master
-
- Stalled
-
-
MDEV-18983 Port rpl_semi_sync_master_wait_for_slave_count from MySQL
-
- Stalled
-