ignite-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From dkarachentsev <dkarachent...@gridgain.com>
Subject Re: Server Node Stops Unexpectedly
Date Fri, 25 Nov 2016 14:35:02 GMT

Node could be segmented if it doesn't respond during some time. The most
common reasons for that:
1) Long GC pause.
2) Operation system could slow down process (f.e. starts swap to disk
process memory).
3) Network issues.

To find out the actual reason you should take GC logs (-XX:+PrintGCDetails
-XX:+PrintGCTimeStamps -XX:+PrintGCDateStamps -XX:+UseGCLogFileRotation
-XX:NumberOfGCLogFiles=10 -XX:GCLogFileSize=100M -Xloggc:/path/to/gc.log
dstat (dstat –t --top-mem –m –s –g –d --fs --top-io 3 > dstat.log) and
ignite logs.

Of course you're free to tune timeouts, it worth to start from
IgniteConfiguration.setFailureDetectionTimeout(), by default it is 10 sec.


View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Server-Node-Stops-Unexpectedly-tp9189p9198.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

View raw message