xtern commented on code in PR #7093: URL: https://github.com/apache/ignite-3/pull/7093#discussion_r2575739455
########## docs/_docs/developers-guide/clients/jdbc-driver.adoc: ########## @@ -72,6 +72,11 @@ jdbc:ignite:thin://host[:port][,host[:port][/schema][[?parameter1=value1][;param ** `partitionAwarenessMetadataCacheSize` - Size of cache to store partition awareness metadata of queries, in number of entries. Default value: `1024`. ** `queryTimeout` - Number of seconds the driver will wait for a `Statement` object to execute. 0 means there is no limit. Default value: `0`. ** `connectionTimeout` - Number of milliseconds JDBC client will wait for server to respond. 0 means there is no limit. Default value: `0`. +** `backgroundReconnectInterval` - Background reconnect interval, in milliseconds. The value `0` can be used to disable background reconnection. Default value is `30000` (30 seconds). +Background reconnection is used to restore old and establish new connections to cluster nodes in the background. +For example, if you disable it, the client will not try to restore connections to temporarily unavailable cluster nodes. +** `reconnectRetriesLimit` - Maximum number of *retry* attempts to establish connection. The value `0` means that no retries will be made. The value `-1` means that the number of retries is not limited. Default value is `16`. Review Comment: But as for your question, no, the retry counter applies only to a specific operation. Let's say the connection to the server was interrupted while retrieving the list of tables, and if the retry counter is greater than 0, we will still try to retry the operation. Thus, if the connection is broken again, the counter starts from zero again. ########## docs/_docs/developers-guide/clients/jdbc-driver.adoc: ########## @@ -72,6 +72,11 @@ jdbc:ignite:thin://host[:port][,host[:port][/schema][[?parameter1=value1][;param ** `partitionAwarenessMetadataCacheSize` - Size of cache to store partition awareness metadata of queries, in number of entries. Default value: `1024`. ** `queryTimeout` - Number of seconds the driver will wait for a `Statement` object to execute. 0 means there is no limit. Default value: `0`. ** `connectionTimeout` - Number of milliseconds JDBC client will wait for server to respond. 0 means there is no limit. Default value: `0`. +** `backgroundReconnectInterval` - Background reconnect interval, in milliseconds. The value `0` can be used to disable background reconnection. Default value is `30000` (30 seconds). +Background reconnection is used to restore old and establish new connections to cluster nodes in the background. +For example, if you disable it, the client will not try to restore connections to temporarily unavailable cluster nodes. +** `reconnectRetriesLimit` - Maximum number of *retry* attempts to establish connection. The value `0` means that no retries will be made. The value `-1` means that the number of retries is not limited. Default value is `16`. Review Comment: But as for your question, no, the retry counter applies only to a specific operation. Let's say the connection to the server was interrupted while retrieving the list of tables, and if the retry counter is greater than 0, we will still try to retry the operation. Next time, if the connection is broken again, the counter starts from zero again. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
