[MXS-1937] Failover/switchover does not disable/enable server events Created: 2018-06-21 Updated: 2021-04-25 Resolved: 2018-09-18 |
|
| Status: | Closed |
| Project: | MariaDB MaxScale |
| Component/s: | failover, mariadbmon |
| Affects Version/s: | 2.2 |
| Fix Version/s: | 2.3.0 |
| Type: | Bug | Priority: | Major |
| Reporter: | Richard Stracke | Assignee: | Esa Korhonen |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Issue Links: |
|
||||||||
| Sprint: | MXS-SPRINT-65, MXS-SPRINT-66 | ||||||||
| Description |
|
Failover and switchover currently do not notice server events at all. This means that on the promoted server, all event states and the variable 'events_scheduler' are the same as on the old master and vice versa. Currently events will be disabled on new master and must be activated manually. |
| Comments |
| Comment by Claudio Nanni [ 2020-09-11 ] |
|
esa.korhonen Reasonable doubt. I think whether the scheduler is enabled or not is responsibility of the DBA(event_scheduler=ON in the config) or Application Developers, but in any case it won't cause data discrepancy. While what should be avoided is an EVENT meant for the whole setup (that must propagate from Master to the Slaves) to be running only on one Slave. For this you can discern using the naming of the STATUS. If the user has disabled it the status is: DISABLED If the replication has disabled it the status is: SLAVESIDE_DISABLED |