[
https://issues.apache.org/jira/browse/IGNITE-7282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16421816#comment-16421816
]
Pavel Tupitsyn commented on IGNITE-7282:
----------------------------------------
1) I think I agree, we should be consistent with other config APIs.
> instead of having three properties Host, Port and Endpoints, we can have
> only one - Endpoints
{{Host}} and {{Port}} are already in 2.4, do you suggest to make them obsolete
(deprecated)?
2) This property applies also when only one endpoint is defined: should we
reconnect in case when connection has dropped or not.
3) This is not an internal detail since user provides us with a list of
endpoints. They might want to know which of these provided endpoints is in use,
I think this makes the API symmetrical.
> .NET: Thin client: Failover
> ---------------------------
>
> Key: IGNITE-7282
> URL: https://issues.apache.org/jira/browse/IGNITE-7282
> Project: Ignite
> Issue Type: Improvement
> Components: platforms, thin client
> Affects Versions: 2.4
> Reporter: Pavel Tupitsyn
> Assignee: Pavel Tupitsyn
> Priority: Major
> Labels: .NET
> Fix For: 2.5
>
>
> Currently user has to manually connect to some specific Ignite server.
> Implement some kind of automatic failover where Thin Client knows about
> multiple nodes.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
