jeremyaouad opened a new pull request, #11950: URL: https://github.com/apache/ignite/pull/11950
Ignite thin client has a seemingly incoherent behavior for determining the serializer of a user defined type. On thin client startup, the passed binary configuration, is taken into account when registering the type descriptors. For each binary type configuration, the type is registered along with its specified serializer, rather than the default serializer being chosen for it. This is not what is happening, however, in the following case: A thin client is connected to 2 servers. One of the servers crashes (chaos testing). The reliable channel fail listener is invoked which cleans up registered type descriptors. When a type that was initially configured in the binary config along with its serializer is used, the type descriptor will be recreated, passing through the method defaultSerializer, which only returns the default serializer if defined, ignoring whether or not a specific config has been specified for the class. In this pr, I align the behavior at startup with the behavior after a server crash. -- 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: notifications-unsubscr...@ignite.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
