Drivers: Unified login timeout parameters
Details
| Detail name | Value |
|---|---|
| Changelog Number | 14618 |
| Type | Improvement |
| Status | Resolved |
| Fix Versions | Exasol 7.1.11, Exasol 8.0.3 |
| Resolution Date | 2022-06-09 |
Background
When the connection string contains more than one node, the driver attempts to connect to each of them sequentially in random order.
For ODBC, JDBC, and ADO.NET the parameters for login/connection timeout behaved differently depending on the driver. For more details on the previous behavior, please see the 7.0 documentation.
Improvement
All drivers (ODBC, JDBC, and ADO.NET) follow this unified behaviour for timeouts:
| Parameter Name | Description |
|---|---|
| hosttimeout | Specifies connection timeout for each TCP connection attempt (in milliseconds). If multiple hosts are specified in the connection string, each host waits for the specified time for a successful connection. The default is 2000. |
| logintimeout | The maximum time (in milliseconds) the driver waits to establish a connection. This timeout is required to limit the overall login time, especially in the case of a large cluster with several reserve nodes. The default value is 0 (infinite). |
| connecttimeout | Deprecated |
The maximum time (milliseconds) spent to connect is the minimum value of
- "number of nodes" * hosttimeout
- logintimeout
Changed behavior
Unified behavior of timeout parameters. Changes for logintimeout, deprecation of connecttimeout and new parameter hosttimeout.
