You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Pavel Tupitsyn (JIRA)" <ji...@apache.org> on 2019/06/06 18:03:00 UTC
[jira] [Commented] (IGNITE-9876) .NET: Thin Client: Implement Best
Effort Affinity
[ https://issues.apache.org/jira/browse/IGNITE-9876?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16857958#comment-16857958 ]
Pavel Tupitsyn commented on IGNITE-9876:
----------------------------------------
[~isapego] checked, the order of nodes is deterministic, the test should not be flaky. Waiting for TC run, then merging.
> .NET: Thin Client: Implement Best Effort Affinity
> -------------------------------------------------
>
> Key: IGNITE-9876
> URL: https://issues.apache.org/jira/browse/IGNITE-9876
> Project: Ignite
> Issue Type: New Feature
> Components: platforms, thin client
> Reporter: Pavel Tupitsyn
> Assignee: Pavel Tupitsyn
> Priority: Major
> Labels: .NET, iep-23
> Time Spent: 20m
> Remaining Estimate: 0h
>
> See linked IEP-23.
> First iteration is going to be an "experimental feature" with the following limitations:
> * No reconnect support for failed nodes
> * No AffinityKeyMapped support
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)