Request among nodes taking minimum of idleConnectionTimeout configuration in tcpcommunicationSpi
This post was updated on .
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
Node i1 logs has information that request was once tried and then next one
was tried after exact 30 sec.
idleConnectionTimeout is configured to 30s, so we think it may be related to
Update:Please also refer to below two message in same thread.
Can someone please clarify
1. why our request was failing intermittently and then after exactly 30 sec
of time it reaches to Prague machine again. It looks like first requests'
TCP communication was idle and timedout then another request went. If yes,
then how can we be sure about the reason.
2. Why the topology has multiple nodes once we add the India Machine info in
3. Should we add IPs of machine in both Prague and India in TCPDiscoverySPI.
Re: Request among nodes taking minimum of idleConnectionTimeout configuration in tcpcommunicationSpi
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.