Setting config "databases-to-replicate" breaks Galera replication
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Percona Cluster Charm |
Fix Released
|
Low
|
Billy Olsen |
Bug Description
When setting "databases-
From the documentation in charmhub, setting this option should not affect Galera synchronous replication.
This issue is currently affecting an ongoing deployment. The main goal is to establish asynchronous replication between two databases and excluding Vault db's from the process.
Environment:
Ubuntu 18.04
cs:percona-
Juju 2.8.11
Steps to reproduce
1) Deploy a percona-cluster with 3 units using the attached bundle
2) make sure the databases-
3) on mysql/0: create a database, a table and insert some values
4) check mysql/1 and mysql/2: database is created but tables are empty
Notes:
A recent version of Galera cluster[1] introduced a new option that allows ignoring native replication filter rules if configured with replicate-do-db.
However, wsrep_mode is only available with Galera 4.0 [2] which was not backported to bionic yet.
[1] https:/
[2] https:/
Changed in charm-percona-cluster: | |
status: | Fix Committed → Fix Released |
Confirmed by looking at the code. The hooks provide the databases_ to_replicate value down to the template engine for the mysql options without first validating that there is an asynchronous replication relation established.
For consideration of backporting the wsrep mode enhancement to Bionic a separate bug will need to be raised.