[MXS-4283] Race condition in KILL command processing Created: 2022-09-07 Updated: 2022-09-09 Resolved: 2022-09-08 |
|
| Status: | Closed |
| Project: | MariaDB MaxScale |
| Component/s: | Protocol |
| Affects Version/s: | 2.5.21, 6.4.2, 22.08.0 |
| Fix Version/s: | 2.5.22, 6.4.3, 22.08.1 |
| Type: | Bug | Priority: | Major |
| Reporter: | markus makela | Assignee: | markus makela |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Issue Links: |
|
||||||||
| Description |
|
Under heavy load MaxScale might crash if a KILL command is executed that ends up killing at least one backend connection. This happens due to a race condition in the event delivery where the calling code doesn't correctly increment the reference counts. This was introduced in commit 51eabc8f6f33cb471e59f6fd4b37c642f6726150. |