ignite-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ilya.kasnacheev" <ilya.kasnach...@gmail.com>
Subject Re: Socket Reader Timeout on ClientImpl
Date Fri, 01 Dec 2017 09:28:31 GMT
Hello Tolga!

First of all, Ignite has two kinds of connections: Discovery connections and
Communication connections.

Discovery connections form a ring and make sure node requires topology
updates, Communication connections established between nodes and are used to
pass data.

ClientImpl should not be your concern here, as it reads from Discovery
socket and it's normal mode of operation to wait on socket.

What should concern you is Communication timeouts, you can set
socketWriteTimeout and connectTimeout on TcpCommunicationSpi in Ignite
configuration. However in your case it's likely that hang is not related to
network problems. Please consider logs of your nodes - any thread pool
starvation messages? Exceptions? Failures to wait for exchanges?

In your case there's likely to be the latter:
	- parking to wait for  <0x00000007d9608000> (a
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture)

Some node is unable to finish exchange due to long running transactions or
other problems, please scoop logs carefully for errors, post the most
interesting findings here. The exchange in question was likely initiated by
attempting to start a new cache, as apparent by:

	- parking to wait for  <0x00000007d964b7a8> (a
org.apache.ignite.internal.processors.cache.GridCacheProcessor$DynamicCacheStartFuture)

Regards,



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

Mime
View raw message