Hi Val, without the eviction policy, the setup breaks due to java.lang.OutOfMemoryError: GC overhead limit exceeded
I'm not sure why the heap grows (+ it looks like GC can't free it), in case of the mentioned (off-heap) config. In the end almost everything should be stored off-heap. However, maybe it's a kind of index which needs heap-space. In that case it would be great to know how much heap-space is safe if the off-heap size should be ~50 GB. Kind regards Peter 2016-06-28 21:14 GMT+02:00 vkulichenko <[email protected]>: > Peter, > > The only configuration that defines whether nodes join topology or not is > discovery SPI (the one you provided in the first message) > > All looks fine, expect that eviction policy will be ignored in your case. > It's used for entries that are stored in heap memory, while your cache is > OFFHEAP_TIERED and therefore stores everything offheap. > > -Val > > > > -- > View this message in context: > http://apache-ignite-users.70518.x6.nabble.com/Non-cluster-mode-tp5959p5978.html > Sent from the Apache Ignite Users mailing list archive at Nabble.com. >
