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 2023/06/23 12:34:00 UTC

[jira] [Updated] (IGNITE-19826) .NET: Thin 3.0: Partition awareness uses wrong node id

     [ https://issues.apache.org/jira/browse/IGNITE-19826?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Pavel Tupitsyn updated IGNITE-19826:
------------------------------------
    Description: 
There is a confusion between *Local Node ID* (which we get from ConnectionContext.ClusterNode.Id) and *Consistent Node ID* (which is the same as Node Name, comes from ConnectionContext.ClusterNode.Name). Partition assignment (returned by ClientTablePartitionAssignmentGetRequest on the server) is based on *Consistent Node ID*.

All partition awareness tests use FakeServer, so we never tested that it actually works.

> .NET: Thin 3.0: Partition awareness uses wrong node id
> ------------------------------------------------------
>
>                 Key: IGNITE-19826
>                 URL: https://issues.apache.org/jira/browse/IGNITE-19826
>             Project: Ignite
>          Issue Type: Bug
>          Components: platforms, thin client
>    Affects Versions: 3.0.0-beta1
>            Reporter: Pavel Tupitsyn
>            Assignee: Pavel Tupitsyn
>            Priority: Blocker
>              Labels: .NET, ignite-3
>             Fix For: 3.0.0-beta2
>
>
> There is a confusion between *Local Node ID* (which we get from ConnectionContext.ClusterNode.Id) and *Consistent Node ID* (which is the same as Node Name, comes from ConnectionContext.ClusterNode.Name). Partition assignment (returned by ClientTablePartitionAssignmentGetRequest on the server) is based on *Consistent Node ID*.
> All partition awareness tests use FakeServer, so we never tested that it actually works.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)