It is magic, now DistributedSetDemo for new node shows size() == 0. Since there is no backup configured for the set it’s a normal situation when the set is empty after all the nodes that held its data had left the topology. Please note, that the set as a data structure is not removed in such a case, to remove the set completely set.close() method has to be used. However I could reproduce the issue with wrong cache size when the second node is started.
Here is the ticket: https://issues.apache.org/jira/browse/IGNITE-3373 Hope that someone from the community will fix it soon. -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Strange-collocated-distributed-set-behavior-tp5643p5925.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.
