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

Posted to issues@ignite.apache.org by "Denis Magda (JIRA)" <ji...@apache.org> on 2017/05/23 15:53:04 UTC

[jira] [Commented] (IGNITE-5277) Asynchronously establish connection to all the needed nodes in IgniteH2Indexing.send()

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

Denis Magda commented on IGNITE-5277:
-------------------------------------

The discussion on the dev list: http://apache-ignite-developers.2346864.n4.nabble.com/Inefficient-approach-to-executing-remote-SQL-queries-td17882.html

> Asynchronously establish connection to all the needed nodes in IgniteH2Indexing.send()
> --------------------------------------------------------------------------------------
>
>                 Key: IGNITE-5277
>                 URL: https://issues.apache.org/jira/browse/IGNITE-5277
>             Project: Ignite
>          Issue Type: Improvement
>            Reporter: Sergi Vladykin
>
> it's only a minor optimization until the point when establishing each connection takes 3-4 seconds, and we establish 32 of them in sequence.  At that point it becomes a serious issue: the customer cannot run SQL queries from their development machines



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)