[MXS-4679] Binlog Router replication breaks without semi-sync set on Primary Created: 2023-07-21 Updated: 2023-08-15 Resolved: 2023-08-15 |
|
| Status: | Closed |
| Project: | MariaDB MaxScale |
| Component/s: | binlogrouter |
| Affects Version/s: | 23.02.2 |
| Fix Version/s: | N/A |
| Type: | Bug | Priority: | Minor |
| Reporter: | Jonathan Bell | Assignee: | markus makela |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Environment: |
Debian Buster |
||
| Issue Links: |
|
||||||||
| Description |
|
I'm running MaxScale 23.02.2 and it's connected to a Mariadb 10.3.38. Both hosts are on Debian Buster. If rpl_semi_sync_master_enabled is set to false on the primary, replication between MaxScale's binlogrouter and the primary will break within 5 minutes.
If I enable rpl_semi_sync_master_enabled, replication works as expected. The Binlogrouter docs state that semi-sync isn't supported. My MaxScale config looks like this.
The primary's settings are almost entirely the default
|
| Comments |
| Comment by markus makela [ 2023-07-24 ] |
|
I think this is a duplicate of |
| Comment by markus makela [ 2023-08-15 ] |
|
Duplicate of |