Hi, Yes, I can reproduce the behavior. It could be an issue with the custom binary mappers.
The weird thing is that the CustomBinaryIdMapper works fine with a single node, i.e. if it reads and writes the value from a cache, then the mapper is working. But fails on the other node. Meanwhile, it's quite interesting, why do you want to replace the default mapper with a custom one? What tasks are you trying to solve? ----- Alex Shapkin -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/
