Re: Strange node fail

[dkarachentsev]

Duplicates
http://apache-ignite-users.70518.x6.nabble.com/Strange-node-fail-td21078.html.



--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Strange node fail

[dkarachentsev]

Hi Ray,

If your JVM process consumes more memory, then started swapping may cause
JVM freeze, and as a consequence, throwing it out from the cluster. Check
your free memory, disable swapping, if possible, or increase
IgniteConfiguration.failureDetectionTimeout.

To check that guess you may use dstat and add
-XX:+PrintGCApplicationStoppedTime property, it will log additional process
stop times.

Thanks!
-Dmitry



--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Strange node fail

[Ray]

I'm running two cluster on the same 8 nodes, one cluster with native
persistence enabled and the other one is memory only.
The only difference between these two cluster is that the cluster with
native persistence enabled has larger JVM heap than the other one.
The two nodes in the cluster with native persistence enabled failed today, I
looked at the log and GC log and found nothing strange.
I suspect because of the larger JVM heap, the GC takes a lot of time and
then the node is kicked out.
But I found nothing special in the GC log.
Please see the attachment for detailed log information.

node2gc.log
  
node2.log
  
node1gc.log
  
node1.log
  



--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/