FWIW, in our case, the GC was not the problem with Ignite. The heap issue
was already diagnosed, well known and unrelated. The problem was that the
slow down in one node was causing all the other nodes in the grid to
basically lock when reading from the cache, without suffering any GC issue.
A simple problem in one node should not be able to cause your grid to go
down, specially when talking about replicated caches.
GC issues, unrelated to Ignite, will probably appear associated with the
problem because it's one of the most common ways a Java app slows down
without dying completely.
2016-09-16 18:19 GMT+02:00 Ignitebie [via Apache Ignite Users] <
> That would be topic for discussion on how off heap actually work. My
> understanding is to start with object creation will happen on heap (YG)
> and then moved to Old or Off heap.
> If allocation of object creation (I believe after that only you will
> associating them in a map (key.value cache), is quit high, say larger than
> YG size , per sec, then application will be engaged in GC triggered due to
> not being able to allocation.
> Do you see GC trigerred for YG and messages such as Allocation Failure.
> Have you enabled GC logging.
> On Fri, Sep 16, 2016 at 2:47 PM, yfernando <[hidden email]
> <http:///user/SendEmail.jtp?type=node&node=7807&i=0>> wrote:
>> Thanks for your reply Anmol. Do you know if there is a bug logged against
>> this which we can track?
>> Also it's not clear why the nodes would require to GC because all the
>> are held off-heap and we have a 10G heap running G1GC.
>> View this message in context: http://apache-ignite-users.705
>> Sent from the Apache Ignite Users mailing list archive at Nabble.com.
> If you reply to this email, your message will be added to the discussion
> To unsubscribe from One failing node stalling the whole cluster, click
View this message in context:
Sent from the Apache Ignite Users mailing list archive at Nabble.com.