debugsqlMinor
Galera not working with Replication
Viewed 0 times
withworkingreplicationgaleranot
Problem
I am using MariaDB 10.2
I have node2 (2.2.2.2) running as a slave to some external database. I bootstrapped node2 as the first member of a Galera cluster "my_cluster".
Node1 (1.1.1.1) joined with rsync SST but after an hour I see that it's behind node2.
I tried running some inserts manually and it works both ways.
However anything added by the replication to node2 in completely ignored by node1.
node1:
```
MariaDB [db1]> SHOW STATUS LIKE 'wsrep%';
+------------------------------+--------------------------------------+
| Variable_name | Value |
+------------------------------+--------------------------------------+
| wsrep_apply_oooe | 0.000000 |
| wsrep_apply_oool | 0.000000 |
| wsrep_apply_window | 0.000000 |
| wsrep_causal_reads | 0 |
| wsrep_cert_deps_distance | 0.000000 |
| wsrep_cert_index_size | 0 |
| wsrep_cert_interval | 0.000000 |
| wsrep_cluster_conf_id | 6 |
| wsrep_cluster_size | 2 |
| wsrep_cluster_state_uuid | 09e3b6c8-343c-11e8-87cf-07a9813fdf95 |
| wsrep_cluster_status | Primary |
| wsrep_commit_oooe | 0.000000 |
| wsrep_commit_oool | 0.000000 |
| wsrep_commit_window | 0.000000 |
| wsrep_connected | ON |
| wsrep_desync_count | 0 |
| wsrep_evs_delayed | |
| wsrep_evs_evict_list | |
| wsrep_evs_repl_latency
I have node2 (2.2.2.2) running as a slave to some external database. I bootstrapped node2 as the first member of a Galera cluster "my_cluster".
Node1 (1.1.1.1) joined with rsync SST but after an hour I see that it's behind node2.
I tried running some inserts manually and it works both ways.
However anything added by the replication to node2 in completely ignored by node1.
node1:
```
MariaDB [db1]> SHOW STATUS LIKE 'wsrep%';
+------------------------------+--------------------------------------+
| Variable_name | Value |
+------------------------------+--------------------------------------+
| wsrep_apply_oooe | 0.000000 |
| wsrep_apply_oool | 0.000000 |
| wsrep_apply_window | 0.000000 |
| wsrep_causal_reads | 0 |
| wsrep_cert_deps_distance | 0.000000 |
| wsrep_cert_index_size | 0 |
| wsrep_cert_interval | 0.000000 |
| wsrep_cluster_conf_id | 6 |
| wsrep_cluster_size | 2 |
| wsrep_cluster_state_uuid | 09e3b6c8-343c-11e8-87cf-07a9813fdf95 |
| wsrep_cluster_status | Primary |
| wsrep_commit_oooe | 0.000000 |
| wsrep_commit_oool | 0.000000 |
| wsrep_commit_window | 0.000000 |
| wsrep_connected | ON |
| wsrep_desync_count | 0 |
| wsrep_evs_delayed | |
| wsrep_evs_evict_list | |
| wsrep_evs_repl_latency
Solution
Your node2 needs to have
See also SeveralNines' article on the topic which states:
log-slaves-updates=1 is necessary for the writes to propagate from the slave to the other galera nodes
log-slave-updates=1. See also SeveralNines' article on the topic which states:
log-slaves-updates=1 is necessary for the writes to propagate from the slave to the other galera nodes
Context
StackExchange Database Administrators Q#202920, answer score: 3
Revisions (0)
No revisions yet.