[
https://issues.apache.org/jira/browse/IGNITE-27134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18040260#comment-18040260
]
Pavel Pereslegin commented on IGNITE-27134:
-------------------------------------------
We should introduce other properties (which are present in the thin client -
backgroundReconnectInterval and connectionRetryLimit) and use RetryReadPolicy
instead of RetryLimitPolicy when building the client.
> Jdbc. Unsupported connection properties reconnectThrottlingPeriod,
> reconnectThrottlingRetries
> ---------------------------------------------------------------------------------------------
>
> Key: IGNITE-27134
> URL: https://issues.apache.org/jira/browse/IGNITE-27134
> Project: Ignite
> Issue Type: Bug
> Components: jdbc ai3
> Reporter: Pavel Pereslegin
> Priority: Major
> Labels: ignite-3
>
> Apache Ignite 3.1 JDBC documentation
> [mentions|https://ignite.apache.org/docs/ignite3/latest/developers-guide/clients/jdbc-driver#setting-up]
> unsupported properties:
> {noformat}
> reconnectThrottlingPeriod - Reconnect throttling period, in milliseconds. 0
> means there is no limit. Default value: 30_000.
> reconnectThrottlingRetries - Reconnect throttling retries. 0 means there is
> no limit. Default value: 3.
> {noformat}
> We need to remove the mention of them, or add support for them.
> Regarding support,
> {{reconnectThrottlingPeriod}} can be used to specify the thin client's
> {{backgroundReconnectInterval}}.
> {{reconnectThrottlingRetries}} can be used to set max attempts of
> {{RetryLimitPolicy}}.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
