[MXS-4380] Debug assertion in mxs1926_killed_server Created: 2022-11-07 Updated: 2022-11-24 Resolved: 2022-11-24 |
|
| Status: | Closed |
| Project: | MariaDB MaxScale |
| Component/s: | test |
| Affects Version/s: | 6.4 |
| Fix Version/s: | 2.5.23, 6.4.4, 22.08.3 |
| Type: | Task | Priority: | Major |
| Reporter: | markus makela | Assignee: | markus makela |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Sprint: | MXS-SPRINT-170, MXS-SPRINT-171 |
| Description |
|
2022-11-07 11:33:43 error : (2) debug assert at /home/timofey_turenko_mariadb_com/MaxScale/server/modules/protocol/MariaDB/mariadb_backend.cc:2603 failed: !session_is_load_active(m_session) || m_reply.state() == ReplyState::LOAD_DATA_END |
| Comments |
| Comment by markus makela [ 2022-11-21 ] |
|
Appeared to fail in 2.5 as well. |
| Comment by markus makela [ 2022-11-21 ] |
|
Turns out the debug assertion is just faulty: the global state of the LOAD DATA LOCAL INFILE is not related to the state of an individual connection. The failure in 2.5 is caused by the same situation but it manifests as an actual problem as the code ends up skipping the query result tracking which in turn causes the Unexpected result state error and a debug assertion. |