[MDEV-9855] log_slave_updates is required for wsrep_gtid_mode Created: 2016-03-31 Updated: 2019-05-23 Resolved: 2019-05-23 |
|
| Status: | Closed |
| Project: | MariaDB Server |
| Component/s: | Galera, Replication |
| Affects Version/s: | 10.1.13 |
| Fix Version/s: | N/A |
| Type: | Bug | Priority: | Major |
| Reporter: | Geoff Montee (Inactive) | Assignee: | Jan Lindström (Inactive) |
| Resolution: | Not a Bug | Votes: | 0 |
| Labels: | galera, gtid, replication | ||
| Issue Links: |
|
||||||||||||
| Description |
|
When wsrep_gtid_mode is ON, transactions replicated via Galera Cluster's replication should increment the GTID in the domain given by wsrep_gtid_domain_id on all nodes. This only seems to happen on all nodes if log_slave_updates is enabled. For example, let's say that we have a 2-node Galera Cluster: Node 1:
Node 2:
Now let's see how gtid_binlog_pos changes on each node. Node 1:
Node 2:
Let's try again with log_slave_updates enabled. Node 1:
Node 2:
|
| Comments |
| Comment by Geoff Montee (Inactive) [ 2016-04-01 ] |
|
I also just reported |
| Comment by Jan Lindström (Inactive) [ 2019-05-23 ] |
|
I would say this is not a bug. However, documentation could be improved on this area. greenman Can you update the documentation. Note that full GTID support is still to be announced later see https://jira.mariadb.org/browse/MDEV-10715 |
| Comment by Geoff Montee (Inactive) [ 2019-05-23 ] |
|
This is already documented here: |