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] [Comment Edited] (IGNITE-11258) JDBC Thin: update connection setup logic.
Date Wed, 13 Feb 2019 12:36:00 GMT

    [ https://issues.apache.org/jira/browse/IGNITE-11258?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16767124#comment-16767124

Alexander Lapin edited comment on IGNITE-11258 at 2/13/19 12:35 PM:

[~vozerov] Ready for preliminary review.
Please, pay attention, that given ticket also contains changes from IGNITE-11257.

was (Author: alapin):
[~vozerov] Ready for preliminary review.

> JDBC Thin: 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
>            Priority: Major
>              Labels: iep-23
>          Time Spent: 10m
>  Remaining Estimate: 0h
> # 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

View raw message