[MXS-4906] MonitorWorker::call_run_one_tick() called more often than intended Created: 2023-12-18 Updated: 2024-01-02 Resolved: 2024-01-02 |
|
| Status: | Closed |
| Project: | MariaDB MaxScale |
| Component/s: | Monitor |
| Affects Version/s: | 2.5.29, 6.4.13, 22.08.11, 23.02.8, 23.08.4 |
| Fix Version/s: | 2.5.30, 6.4.14, 22.08.12, 23.02.9, 23.08.5 |
| Type: | Bug | Priority: | Minor |
| Reporter: | Esa Korhonen | Assignee: | Esa Korhonen |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Description |
|
The delayed call which checks if a monitor should run a tick is not canceled when stopping monitor (e.g. for reconfiguration). If the monitor thread then starts again, another delayed call starts in addition to the one already scheduled. MonitorWorker::call_run_one_tick() is thus ran twice per 100ms. I.e. each time the monitor is restarted an additional delayed call is added. |