Hi, java.lang.OutOfMemoryError: GC overhead limit exceeded
This kind of OOM exception says that your application spends almost all its time garbage collecting the heap. The first obvious reason is a small heap size and high allocation rate of objects in the heap. Please refer to the page Alexei provided you below and adjust your heap size accordingly. — Denis > On Jun 10, 2016, at 4:46 PM, Alexei Scherbakov <[email protected]> > wrote: > > 1. Affinity function is always present. > By default it's RendezvousAffinityFunction with 1024 partitions. > > 2 OutOfMemory error is only possible when you are running out of free space > in heap > and GC was not able to clean some on allocation request. > > Make sure you tune the GC properly as described here [1] > > [1] https://apacheignite.readme.io/docs/jvm-and-system-tuning > <https://apacheignite.readme.io/docs/jvm-and-system-tuning> > > > 2016-06-10 14:40 GMT+03:00 pragmaticbigdata <[email protected] > <mailto:[email protected]>>: > Thanks Alexei for your inputs. > > 1. How does the EntryProcessor detect which node does the data reside given > the key? I question it because I have configured I have PARTITIONED cache > for which I haven't set any affinity function. It is partitioning the cache > based on the hash function of the cached object. I didn't not follow how > does ignite detect the partition just given the cache key? > > 2. I doubt that the EntryProcessor code is failing because memory is > insufficient. I pulled out the node statistics before starting the test and > verified that there is sufficient heap space available. Please find the > statistics as below. > > visor> node > Select node from: > +=======================================================================================+ > | # | Node ID8(@), IP | Node Type | Up Time | CPUs | CPU Load > | Free Heap | > +=======================================================================================+ > | 0 | 9B989E4C(@n0), <ip1> | Server | 01:59:48 | 2 | 0.33 % | 89.00 > % | > | 1 | 1ED58F00(@n2), <ip2> | Server | 01:59:12 | 4 | 0.17 % | 77.00 > % | > | 2 | 56214422(@n3), <ip3> | Server | 01:57:42 | 2 | 0.33 % | 92.00 > % | > | 3 | A57219B6(@n1), <ip4> | Server | 01:57:25 | 4 | 0.50 % | 87.00 > % | > > > Could you detail on how do EntryProcessor's work? If it was suppose to > execute on the node where the data resides why does crash or take > exponentially more time than it would take with executing any affinity code? > > Thanks. > > > > -- > View this message in context: > http://apache-ignite-users.70518.x6.nabble.com/Simulating-Graph-Dependencies-With-Ignite-tp5282p5572.html > > <http://apache-ignite-users.70518.x6.nabble.com/Simulating-Graph-Dependencies-With-Ignite-tp5282p5572.html> > Sent from the Apache Ignite Users mailing list archive at Nabble.com. > > > > -- > > Best regards, > Alexei Scherbakov
