[MDEV-29785] Duplicate gtid event in binlog Created: 2022-10-13 Updated: 2022-10-19 |
|
| Status: | Open |
| Project: | MariaDB Server |
| Component/s: | Galera, Replication |
| Affects Version/s: | 10.4.26 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major |
| Reporter: | Jesse | Assignee: | Angelique Sklavounos (Inactive) |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Environment: |
RHEL7 derivate, 3 node galera cluster |
||
| Attachments: |
|
| Description |
|
As the GTIDs drift during upgrade process of a galera node (mysql_upgrade --skip-write-binlog --system-tables) and to resynchonize the nodes I ran:
With 10.4.26 the gtid set event was recorded twice in the binlog causing binlog replication to stop. This is a new bug introduced after 10.4.21 as previous upgrades using the same method worked fine. 10.5.17 with set session wsrep_gtid_seq_no is not affected. Workaround: |
| Comments |
| Comment by Angelique Sklavounos (Inactive) [ 2022-10-14 ] | ||||||||||||||||||||||||||||||||||
|
Hi ospi Thank you for the report. I will try to reproduce, but could I please get more details on the replication topology of the setup? Also, what is show slave status output when replication stops? Thank you. | ||||||||||||||||||||||||||||||||||
| Comment by Jesse [ 2022-10-18 ] | ||||||||||||||||||||||||||||||||||
|
Actually this isn't galera related. More likely wsrep_gtid_mode related bug Steps to reproduce with podman
Podman steps
|