[MXS-1381] max_slave_replication_lag should be in mysqlmon, not readwritesplit Created: 2017-08-31 Updated: 2023-05-08 Resolved: 2020-01-20 |
|
| Status: | Closed |
| Project: | MariaDB MaxScale |
| Component/s: | N/A |
| Affects Version/s: | None |
| Fix Version/s: | N/A |
| Type: | Task | Priority: | Major |
| Reporter: | markus makela | Assignee: | markus makela |
| Resolution: | Won't Do | Votes: | 1 |
| Labels: | None | ||
| Issue Links: |
|
||||||||
| Epic Link: | Monitor Improvements | ||||||||
| Description |
|
The MySQL monitor should handle slave servers that are too much behind the master. By removing the Slave status from any server that lags too far behind, the same functionality is achieved that is currently in the readwritesplit. This also allows for some rudimentary IO health checks by checking that the insert into the heartbeat table can be done. If it can't be done then the master is not fully functional. |
| Comments |
| Comment by markus makela [ 2020-01-20 ] |
|
It's better to have this in the router than in the monitor. |
| Comment by Maikel Punie [ 2020-01-20 ] |
|
can we then add the same config option in the readService? as its missing there and can be usefull in that router to. |
| Comment by markus makela [ 2020-01-20 ] |
|
Yes, that can be added as a feature request. |