ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alexander Lapin (JIRA)" <j...@apache.org>
Subject [jira] [Created] (IGNITE-11258) JDBC: update connection setup logic.
Date Fri, 08 Feb 2019 09:20:00 GMT
Alexander Lapin created IGNITE-11258:
----------------------------------------

             Summary: JDBC: update connection setup logic.
                 Key: IGNITE-11258
                 URL: https://issues.apache.org/jira/browse/IGNITE-11258
             Project: Ignite
          Issue Type: Task
          Components: sql
            Reporter: Alexander Lapin


# On thin client startup it connects to *all* *nodes* provided by user by client configuration.
 # Upon handshake server returns its UUID to client.
 # By the end of the startup procedure, client have open connections to all available server
nodes and the following mapping (*nodeMap*): [UUID => Connection].

Connection to all nodes helps to identify available nodes, but can lead to significant delay,
when thin client is used on a large cluster with a long IP list provided by user. To lower
this delay, asynchronous establishment of connections can be used.
For more information see [IEP-23: Best Effort Affinity|https://cwiki.apache.org/confluence/display/IGNITE/IEP-23%3A+Best+Effort+Affinity+for+thin+clients]



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message