Details
-
Bug
-
Status: In Review (View Workflow)
-
Major
-
Resolution: Unresolved
-
25.10, 26.10
-
None
-
None
-
MXS-SPRINT-283
Description
The status of a service using the Exasol or GridGain router is set when MaxScale starts and never changes, so the service appears to be running also when Exasol or GridGain cannot be reached. Consequently SmartRouter keeps connecting to it, and each attempt takes until the ODBC login timeout to fail. A failure to connect is also reported as permanent, so SmartRouter does not use the target again in that session, even if it becomes available.
Attachments
Issue Links
- relates to
-
MXS-7703 exasolrouter sessions (also SmartRouter hinted to exasolrouter) do not reconnect to Exasol after an Exasol restart (error 6784)
-
- Closed
-