[MXS-3248] "error : (1672) Unexpected result state" with connection_keepalive Created: 2020-10-21 Updated: 2021-07-01 Resolved: 2020-11-30 |
|
| Status: | Closed |
| Project: | MariaDB MaxScale |
| Component/s: | Core, readconnroute |
| Affects Version/s: | 2.5.4, 2.5.5 |
| Fix Version/s: | 2.5.6 |
| Type: | Bug | Priority: | Major |
| Reporter: | Nilnandan Joshi | Assignee: | markus makela |
| Resolution: | Fixed | Votes: | 1 |
| Labels: | None | ||
| Issue Links: |
|
||||||||
| Sprint: | MXS-SPRINT-119, MXS-SPRINT-120 | ||||||||
| Description |
|
While, testing a newer maxscale version 2.5.4 for some potential bottlenecking and have an error popping into the maxscale log. Users connecting and processing correctly.
|
| Comments |
| Comment by markus makela [ 2020-11-10 ] | |||||||
|
Does this happen with the latest 2.5 release? | |||||||
| Comment by Valerii Kravchuk [ 2020-11-10 ] | |||||||
|
Yes, it happens with 2.5.5 too:
| |||||||
| Comment by Nilnandan Joshi [ 2020-11-26 ] | |||||||
|
If we set connection_keepalive=0s to the services (all) in maxscale.cnf. These errors are gone. | |||||||
| Comment by markus makela [ 2020-11-27 ] | |||||||
|
I managed to reproduce this with https://mariadb.com/kb/en/mariadb_stmt_execute_direct/ when readconnroute is configured with connection_keepalive with a value other than 0s. Since the default is 300s, this should be reproducible with the default configuration. | |||||||
| Comment by markus makela [ 2020-11-27 ] | |||||||
|
Which connector does this happen with? Right now it looks like a case where the resultset tracking used by the connection_keepalive doesn't work correctly when used with readconnroute and batch inserts or execute_direct. |