You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Vadim Pakhnushev (Jira)" <ji...@apache.org> on 2024/04/04 14:00:00 UTC

[jira] [Created] (IGNITE-21989) JDBC URL completer uses outdated topology

Vadim Pakhnushev created IGNITE-21989:
-----------------------------------------

             Summary: JDBC URL completer uses outdated topology
                 Key: IGNITE-21989
                 URL: https://issues.apache.org/jira/browse/IGNITE-21989
             Project: Ignite
          Issue Type: Improvement
          Components: cli
            Reporter: Vadim Pakhnushev
            Assignee: Vadim Pakhnushev


{{JdbcUrlRegistryImpl}} uses {{NodeNameRegistry}} in order to get all nodes URLs. These registries are updated periodically and it so happens that the order is {{JdbcUrlRegistry}} then {{NodeNameRegistry}} so {{JdbcUrlRegistry}} always uses outdated topology information.
For example, after the first connect valid JDBC URL completion happens only after second update which by default happens every 5 seconds.
When node leaves the cluster, this could lead to unwanted delays in updates where {{JdbcUrlRegistry}} tries to connect to the already left node.
This was found when running the {{ItIgnitePicocliCommandsTest#startStopNodeWhenCompleteNodeName}} on Windows, where connect attempt takes a lot of time if the node is stopped.



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