Re: Request among nodes taking minimum of idleConnectionTimeout configuration in tcpcommunicationSpi

2020-07-10 Thread Ilya Kasnacheev
Hello! Maybe you have some firewall issue here, such as only one way connections are possible but not the other way around. We do not recommend geo-distributed clustering with Apache Ignite. Regards, -- Ilya Kasnacheev вт, 7 июл. 2020 г. в 06:59, trans : > Hi, can someone please suggest on

Re: Request among nodes taking minimum of idleConnectionTimeout configuration in tcpcommunicationSpi

2020-07-06 Thread trans
Hi, can someone please suggest on above. Why client is trying to use different port other than its for creating TCP client and failing 30 times Thanks. -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Request among nodes taking minimum of idleConnectionTimeout configuration in tcpcommunicationSpi

2020-07-06 Thread trans
After enabling the debug level logging we notice below Machine in india(10.101.137.123) running on port 56037, but why the tcp client is being tried to create with port 48104. Please note that 48104 is the port of the other node in prague. Could you please point out the things done wrong.

Request among nodes taking minimum of idleConnectionTimeout configuration in tcpcommunicationSpi

2020-07-05 Thread trans
Hi Guys, We have 4 clients(p1,p2,p3,p4) and 1 server running in Prague, then one other node(i1) running in India. But when we communicate from node in India to node in Prague then we see that intermittently the request reaches to Prague after delay of around 30sec. Node i1 logs has information