Details
-
Bug
-
Status: Closed (View Workflow)
-
Critical
-
Resolution: Fixed
-
10.4(EOL), 10.5, 10.6, 10.11, 11.0(EOL), 11.4
Description
Setup
2 Galera cluster, both are connected via async replication.
The Nodes which are connected via async replication works fine.
table Gtid_slave_pos will be replicated, because of the fix in MDEV-31413
With wsrep_gtid_slave_pos disabled the seqno can be different on the nodes,
so the replicated gtid not exists on the other galera nodes and will not be purged, because they will never be processed.
Attachments
Issue Links
- relates to
-
MDEV-34924 gtid_slave_pos table rows newer been deleted on non replica nodes (wsrep_gtid_mode = 1)
- In Review
-
MDEV-31413 Node has been dropped from the cluster on Startup / Shutdown with async replica
- Closed
-
MDEV-31905 WSREP GTID MODE is inconsistent
- Closed