Hi everyone! Ignite has a limitation that it can’t work with custom classes put into metastorage: https://issues.apache.org/jira/browse/IGNITE-13642 If you put a POJO into the metastorage, then Ignite will try to deserialize it using the classes it finds on the classpath. If it can’t do the deserialization, then the node will fail.
There is an opinion that the metastorage wasn’t design for a case when classes that can disappear from Ignite distribution. If we follow this path, then it’s better to limit the metastorage with storing primitives only, so that it’s impossible to occasionally put anything breaking. If a piece of configuration is put into the metastorage by a plugin, then the plugin will be in charge of deserializing the configuration, and not Ignite. Alternatively we can try to fix the metastorage and make it ignore deserialization errors when they occur. What do you think? Denis
