[
https://issues.apache.org/jira/browse/IGNITE-15807?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17573639#comment-17573639
]
Pavel Tupitsyn commented on IGNITE-15807:
-----------------------------------------
[~timonin.maksim]
> this fix breaks balancing
Did we have any kind of "balancing" before? I think the fix preserves existing
logic.
Regarding "primary" addresses: for example, there might be a dynamic cluster
where a few nodes always exist, but other nodes are added/removed based on the
load, so the user might expect us to connect to the specified addresses in the
specified order, not randomly. If the user wants round-robin or random order,
they can reorder the addresses in config easily.
> 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)
