[IGNITE-19827] Java thin 3.0: Partition awareness uses wrong node id

• Type: Bug
• Status: Resolved
• Priority: Blocker
• Resolution: Fixed
• Affects Version/s: 3.0.0-beta1
• Fix Version/s: 3.0
• Component/s: thin client
• Labels: ignite-3

Language

C#

• Assignee: Pavel Tupitsyn
• Reporter: Pavel Tupitsyn
• Reviewer: Igor Sapego
• Created: 23/Jun/23 12:34
• Updated: 04/Sep/24 16:10
• Resolved: 03/Jul/23 07:47

Description

There is a confusion between Local Node ID (which we get from protocolContext().clusterNode().id()) and Consistent Node ID (which is the same as Node Name, comes from protocolContext().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.

Issue Links

• is a clone of: IGNITE-19826 .NET: Thin 3.0: Partition awareness uses wrong node id
• links to: GitHub Pull Request #2276