Re: failureDetectionTimeout tuning

We will try this and get back to you. Does it mean that usually the node recovers from it, if it were due to GC? Would we also have to remove joinTimeout? -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/failureDetectionTimeout-tuning-tp7374p7473.html Sent from

Re: failureDetectionTimeout tuning

of memory or experiencing GC pauses. -Val -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/failureDetectionTimeout-tuning-tp7374p7383.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: failureDetectionTimeout tuning

http://apacheignite.gridgain.org/v1.7/docs/cluster-config#failure-detection-timeout Most likely a hardware or network issue (or your node could be very busy as well). On 8/29/16, 8:54 AM, "bintisepaha" wrote: We see this message logged in our logs from time to

failureDetectionTimeout tuning

have Thanks, Binti -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/failureDetectionTimeout-tuning-tp7374.html Sent from the Apache Ignite