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 2021/11/08 13:12:00 UTC

[jira] [Commented] (IGNITE-15807) In case of port is absent in IgniteClient first of all try connect on default port

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

Pavel Tupitsyn commented on IGNITE-15807:
-----------------------------------------

Cherry-picked to ignite-2.12: 92e56eaeec55fec26c463545c9031449ef872672

> In case of port is absent in IgniteClient first of all try connect on default port
> ----------------------------------------------------------------------------------
>
>                 Key: IGNITE-15807
>                 URL: https://issues.apache.org/jira/browse/IGNITE-15807
>             Project: Ignite
>          Issue Type: Improvement
>          Components: thin client
>    Affects Versions: 2.11
>            Reporter: Ilya Kazakov
>            Assignee: Ilya Kazakov
>            Priority: Minor
>             Fix For: 2.13
>
>          Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> Now if in ClientConfiguration address specified without port, client will try to connect to default port range in random order. But often server listen on default port. This random order leads to unexpected connection time.
> Will be better if firstly client will try to connect to default port, before randomly scan all port range.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)