Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
25.10, 26.10
-
None
-
MXS-SPRINT-282, MXS-SPRINT-283
-
Can result in unexpected behaviour
-
Description
Summary
After the Exasol backend is restarted, client sessions that were already open on the exasolrouter (directly, or through SmartRouter with a hint that routes to exasolrouter) never recover. Every query on such a session fails with error 6784 even though Exasol is accepting connections again. A new client connection works immediately.
Environment
- MaxScale 26.10.0-rc1 (image us-central1-docker.pkg.dev/mariadb-es-docker-registry/docker-proxy-dev/maxscale:26.10.0-rc1)
- MariaDB 11.8, Exasol docker-db 2026.1.0
- exasolrouter listener on :3311, SmartRouter on :3310
Steps to reproduce
- Open a long-lived client session on the exasolrouter listener (:3311), and a second one on SmartRouter (:3310) with the hint /* maxscale route to server exasolrouter */.
- On each, run select count
from flights.flights where id > N every 5 seconds. - Restart the Exasol container (it is back and accepting SQL after about 33 seconds).
Observed
- While Exasol is down: ERROR 49215 (08S01): [Exasol][Exasol Driver]No server listening.
- After Exasol is back, every later query on the same session fails: ERROR 6784 (HY000): [Exasol][Exasol Driver]Database server not connected.
- :3311 session: still failing about 2m40s after Exasol returned (34 consecutive failures).
- :3310 session with the exasolrouter hint: still failing about 2m17s after Exasol returned (32 consecutive failures).
- A new connection to the same listener immediately returns correct results, so reconnecting the client is the only workaround seen.
- An unhinted SmartRouter session kept working through the restart, but only because MariaDB answered every query (Exasol was never involved). Exasol-routed reads through SmartRouter were not tested.
Not tested
- Waits longer than about 3 minutes after Exasol is back.
- Any MaxScale timeout or reconnect settings.
Expected
exasolrouter re-opens its ODBC connection to Exasol after a failure, or closes the client session so that clients reconnect.
Origin
Reported from a MariaDB Cloud deployment: after deleting the Exasol pod and letting it rebuild, existing connections return errors and have to be recreated before data can be queried again.
Created via the jira-create skill.
Attachments
Issue Links
- relates to
-
MXS-7750 Support for changing the user and resetting the connection with the Exasol and GridGain routers
-
- In Review
-
-
MXS-7751 The status of an Exasol or GridGain service does not reflect whether Exasol or GridGain can be reached
-
- In Review
-
-
MXS-7752 Handling of queries by SmartRouter when Exasol or GridGain is unavailable
-
- In Progress
-
- blocks
-
MCDEV-2572 Loading...