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" <[email protected]> wrote: We see this message logged in our logs from time to time. Is this a potential issue with one of the nodes? [tcp-disco-sock-reader-#41%DataGridServer-Staging%] ERROR (Log4JLogger.java:495) Failed to initialize connection [sock=Socket[addr=/10.22.50.193,port=35612,localport=47501]] class org.apache.ignite.spi.IgniteSpiOperationTimeoutException: Network operation timed out. Increase 'failureDetectionTimeout' configuration property [failureDetectionTimeout=10000] at org.apache.ignite.spi.IgniteSpiOperationTimeoutHelper.nextTimeoutChunk(IgniteSpiOperationTimeoutHelper.java:81) at org.apache.ignite.spi.discovery.tcp.ServerImpl$SocketReader.body(ServerImpl.java:5035) at org.apache.ignite.spi.IgniteSpiThread.run(IgniteSpiThread.java:62) How do you recommend fixing it? We are not using networkDetection or failureDetection timeout yet in our configs. This is what we have <property name="discoverySpi"> <bean class="org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi"> <property name="joinTimeout" value="30000"/> <property name="ackTimeout" value="30000"/> <property name="maxAckTimeout" value="60000"/> <property name="reconnectCount" value="5"/> Thanks, Binti -- View this message in context: https://urldefense.proofpoint.com/v2/url?u=http-3A__apache-2Dignite-2Dusers.70518.x6.nabble.com_failureDetectionTimeout-2Dtuning-2Dtp7374.html&d=DQICAg&c=DS6PUFBBr_KiLo7Sjt3ljp5jaW5k2i9ijVXllEdOozc&r=qU_93SngJY3bPFd_cHFzZ8u3Owp9FHXx0iQE6zMz3jc&m=cM4HLc8iuz3WYqm2spb6ArVFF13MZgY5kaWXaY3gVWU&s=PBK9WPMK9Qc5uFqsoylEQRbsOGL93Y2oWiBfNckRRb4&e= Sent from the Apache Ignite Users mailing list archive at Nabble.com.
