Details
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.
Attachments
Issue Links
- is cloned by
-
IGNITE-19827 Java thin 3.0: Partition awareness uses wrong node id
- Resolved
- links to