[MXS-1540] Race conditions in Galeramon server parameter handling Created: 2017-11-24 Updated: 2017-11-24 Resolved: 2017-11-24 |
|
| Status: | Closed |
| Project: | MariaDB MaxScale |
| Component/s: | N/A |
| Affects Version/s: | 2.1.11 |
| Fix Version/s: | 2.1.12 |
| Type: | Bug | Priority: | Critical |
| Reporter: | markus makela | Assignee: | Unassigned |
| Resolution: | Not a Bug | Votes: | 0 |
| Labels: | None | ||
| Description |
|
The Galeramon uses the server parameters at run-time to determine the node priority. As the parameters can be changed at runtime, their usage should be covered by a lock. Currently, they are inspected without locks which causes race conditions on the stored data. |
| Comments |
| Comment by markus makela [ 2017-11-24 ] |
|
Not a bug as the servers are actually locked for the duration of the monitoring interval. As the alteration of the parameters was introduced in 2.1, where the locking was added as well, there is no bug. |