Hello Ignite-Community! I've to use a special (not open) logger in my project. It causes a strange side-effect in Ignite. Once I use it in a method which fills the Off-heap cache via IgniteDataStreamer, the memory consumption is different. Without using the logger the Off-heap-size is ~15MB for 1000 entries. Just adding the logger (it gets called before the work starts) and filling the cache with the same entries leads to an Off-heap size of more than 500MB for the same 1000 entries. I've no idea how Ignite and esp. the consumed size can be impacted by a logger. I reproduced it at least 20 times (adding the log-statement always caused the huge cache-size and removing it resulted in a small cache).
Furthermore, I get a strange message in combination with the logger: "Class java.beans.PropertyChangeSupport cannot be written in binary format because it either implements Externalizable interface or have writeObject/readObject methods. Please ensure that all nodes have this class in classpath. To enable binary serialization either implement Binarylizable interface or set explicit serializer using BinaryTypeConfiguration.setSerializer() method." It just shows up once, but not at the first entry. Also with different data it shows up (just once) and usually not for the first entry. Any hint is appreciated, Peter
