Details
-
New Feature
-
Status: In Progress (View Workflow)
-
Major
-
Resolution: Unresolved
-
25.10, 26.10
-
None
-
None
-
MXS-SPRINT-283
Description
When Exasol or GridGain is unavailable, SmartRouter still routes to it the queries that it has measured to be faster there, and the session is then closed. A query that a hint routes to Exasol or GridGain also closes the session.
A read that times out waiting for a cluster when causal_reads is used is instead handled according to causal_reads_on_timeout: it is routed to the primary or answered with an error, and the session remains usable. There is no corresponding choice when the target is unavailable, although executing a query that is best handled by an analytical engine on the primary may be very expensive.
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
-