Hi, Can you please attach the whole log? Most likely the node was still suffering from GC pauses or OOM and was segmented.
Answering your questions: 1. Yes, data in partitioned cache is evenly split across nodes. But note that there is always Ignite overhead on top of the data itself. Refer to [1] for some details and hints. Also keep in mind that memory is managed by JVM, so part of the heap is usually consumed by garbage which will be eventually collected. So the reported amount of consumed memory is not always accurate. To check this you can use any tool like VisualVM to force garbage collection. After it's done, you will get more informative picture. 2. Client node will connect to one of the addresses provided by the IP finder. There is no single point where all clients connect to. -Val -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Heap-memory-getting-increase-while-doing-cache-get-tp3925p3981.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.
