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

Maksim Timonin edited comment on IGNITE-15807 at 8/1/22 8:35 AM:
-----------------------------------------------------------------

[~ptupitsyn] [~kazakov] 

Hi guys! Could you please explain what is a "primary address" in the PR 
discussion[1] ? It looks like this fix breaks balancing of thin clients 
connection to cluster (by addresses). Is any explanation why this is needed?

I agree that default port should be preferable, but why the first address?

 

In case somebody needs predefined order of addresses, one can use 
ClientAddressFinder that return strict order of addresses.

 

[1] 
[https://github.com/apache/ignite/pull/9522/files/274f488875a9ed8097b3aab2bd30765e8b98373a#r738304340]


was (Author: timonin.maksim):
[~ptupitsyn] [~kazakov] 

Hi guys! Could you please explain what is a "primary address" in the PR 
discussion[1] ? It looks like this fix breaks balancing of thin clients 
connection to cluster (by addresses). Is any explanation why this is needed?

I agree that default port should be preferable, but why the first address?

 

[1] 
https://github.com/apache/ignite/pull/9522/files/274f488875a9ed8097b3aab2bd30765e8b98373a#r738304340

> 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.10#820010)

Reply via email to