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

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

> Did we have any kind of "balancing" before? I think the fix preserves 
>existing logic.

Yes, it chose channel by Random, now it's always 0. See 
`ReliableChannel#initChannelHolders`: now here `dfltChannelIdx = 0` , before it 
was random.

> user might expect us to connect to the specified addresses in the specified 
> order

I believe that user will configure only stable nodes. Otherwise, it can 
configure it with ClientAddressFinder that was implemented for dynamic cases.


was (Author: timonin.maksim):
> Did we have any kind of "balancing" before? I think the fix preserves 
>existing logic.

Yes, it chose channel by Random, not it's always 0. See 
`ReliableChannel#initChannelHolders`: now here `dfltChannelIdx = 0` , before it 
was random.

> user might expect us to connect to the specified addresses in the specified 
> order

I believe that user will configure only stable nodes. In such case, otherwise 
it can configure it with ClientAddressFinder that was implemented for dynamic 
cases.

> 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