You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ignite.apache.org by "Pavel Tupitsyn (Jira)" <ji...@apache.org> on 2023/02/15 11:37:00 UTC

[jira] [Created] (IGNITE-18809) Thin 3.0: Reconnect secondary endpoints in background

Pavel Tupitsyn created IGNITE-18809:
---------------------------------------

             Summary: 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
             Fix For: 3.0.0-beta2


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.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)