LazyServiceConfiguration.equalIgnoreNodeFilter comparing srvcBytes instead of class name breaking node scaling

[austinwellman]

We deploy a cluster of multiple nodes of the same type to scale our services. The changes from IGNITE-17296 (specifically where it is comparing marshaled bytes instead of class name) have resulted in the equalsIgnoreNodeFilter to now return false, resulting in multiple client services of the same type connecting to a common ignite server to fail.

It isn't entirely clear if this is a regression or we are doing something wrong. Looking at the JdkMarshaller and related classes it isn't exactly clear how to resolve this if we are doing something incorrectly.

[xtern]

@austinwellman

resulting in multiple client services of the same type connecting to a common ignite server to fail

I don't quite understand the problem you are facing. Could you provide some more details, for example a step by step scenario (with service configuration description) on how to reproduce this issue?