[
https://issues.apache.org/jira/browse/IGNITE-18809?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Tupitsyn updated IGNITE-18809:
------------------------------------
Description:
On start, Java thin client establishes 1 primary connection in foreground, and
then connects to other known servers in the background. If the primary
connection is lost, it is re-established automatically. However, when secondary
connections are lost, they are not re-established, which means partition
awareness and request balancing may not work as expected.
Use a timer to check and fix secondary connections periodically.
was:
On start, .NET thin client establishes 1 primary connection in foreground, and
then connects to other known servers in the background. If the primary
connection is lost, it is re-established automatically. However, when secondary
connections are lost, they are not re-established, which means partition
awareness and request balancing may not work as expected.
Use a timer to check and fix secondary connections periodically.
> Thin 3.0: Reconnect secondary endpoints in background
> -----------------------------------------------------
>
> Key: IGNITE-18809
> URL: https://issues.apache.org/jira/browse/IGNITE-18809
> Project: Ignite
> Issue Type: Improvement
> Components: platforms, thin client
> Affects Versions: 3.0.0-beta1
> Reporter: Pavel Tupitsyn
> Assignee: Pavel Tupitsyn
> Priority: Major
> Labels: ignite-3
> Fix For: 3.0.0-beta2
>
>
> On start, Java thin client establishes 1 primary connection in foreground,
> and then connects to other known servers in the background. If the primary
> connection is lost, it is re-established automatically. However, when
> secondary connections are lost, they are not re-established, which means
> partition awareness and request balancing may not work as expected.
> Use a timer to check and fix secondary connections periodically.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
