ogronome opened a new issue, #13746: URL: https://github.com/apache/ignite/issues/13746
When forming an Ignite 3.1.0 cluster across `amd64` and `aarch64` nodes, UUIDs appear to be serialized differently depending on CPU architecture. For example, the UUID reported by the remote node is `af432ef1-df56-6352-c325-e32a354e77bf`, while its actual node ID is `526356df-f12e-43af-bf77-4e352ae325c3`. The UUIDs match when the bytes in each 64-bit half are reversed. This suggests architecture-dependent byte ordering in the UUID serialization/deserialization path, potentially involving `GridUnsafe` and `DirectByteBufferStreamImplV1`. The resulting node ID mismatch prevents successful communication and may trigger `RecipientLeftException`. **Expected behavior:** UUIDs and other protocol fields should have a consistent, architecture-independent wire representation so that `amd64` and `aarch64` nodes can safely coexist in the same cluster. Could you confirm whether this is a known issue in Ignite 3.1.0 and whether a fix is available? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
