[
https://issues.apache.org/jira/browse/IGNITE-15807?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Amelchev Nikita updated IGNITE-15807:
-------------------------------------
Fix Version/s: 2.12
(was: 2.13)
> 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.12
>
> 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)
