[MXS-1178] master_accept_reads doesn't work with detect_replication_lag Created: 2017-03-08 Updated: 2017-06-07 Resolved: 2017-03-09 |
|
| Status: | Closed |
| Project: | MariaDB MaxScale |
| Component/s: | readwritesplit |
| Affects Version/s: | None |
| Fix Version/s: | 2.0.6, 2.1.1 |
| Type: | Bug | Priority: | Major |
| Reporter: | markus makela | Assignee: | markus makela |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Description |
|
When the master_accept_reads option for readwritesplit is enabled and the detect_replication_lag parameter is enabled for the mysqlmon, it's possible that the master will never get any reads even if the slave selection criteria is not based on the replication lag. This is fixed by disabling the detect_replication_lag parameter from mysqlmon. |
| Comments |
| Comment by markus makela [ 2017-03-09 ] |
|
The master_accept_reads didn't work if a slave candidate was picked before a master. This prevented master servers from being used for reads if a slave was inspected before a master. |