[MXS-213] Binlog Server Phase 3: Support Semi-Sync Replication in Binlog Server Created: 2015-06-22 Updated: 2016-03-08 Resolved: 2016-03-08 |
|
| Status: | Closed |
| Project: | MariaDB MaxScale |
| Component/s: | binlogrouter |
| Affects Version/s: | None |
| Fix Version/s: | 1.4.0 |
| Type: | New Feature | Priority: | Major |
| Reporter: | VAROQUI Stephane | Assignee: | Massimiliano Pinto (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Sprint: | 1.4.0-1, 1.4.0-2, 2016-4 |
| Description |
|
The mysqlbinlog backup implementation is sharing the code with the server semisync slave plugin. Semi-sync implementation would enable lossless failover by sending backlog events to a candidate slave |
| Comments |
| Comment by Dipti Joshi (Inactive) [ 2015-08-04 ] |
|
This is Phase 3 of binlog server |
| Comment by Dipti Joshi (Inactive) [ 2015-08-13 ] |
|
Massimiliano Pinto Please add estimate |
| Comment by VAROQUI Stephane [ 2016-01-07 ] |
|
What would look nice is to get warning if semi-sync delay is not 3 times monitoring delay . if this condition is true fetching of semi-sync status should be done by the monitoring . If the last monitoring semy-sync status was sync than we know that we did no lost an event on the old master and he can become a candidate slave This would enable failover to work as a switchover if replication is not delayed more than 3 times monitoring delay |
| Comment by Massimiliano Pinto (Inactive) [ 2016-01-08 ] |
|
Current work is in: https://github.com/mariadb-corporation/MaxScale/tree/MXS-213 In maxscale.cnf just put semisync=1 In the Master Server: MySQL>INSTALL PLUGIN rpl_semi_sync_master SONAME 'semisync_master.so'; Check it: |
| Comment by Dipti Joshi (Inactive) [ 2016-03-08 ] |
|
Massimiliano Pintotturenko johan.wikman Which jira item covers the QA test cases for this feature ? Also this was originally planned for 1.5 , not 1.4 |