Hi,
This thread dump is absolutely fine, you confused socket state and java
thread state. These two things are absolutely unrelated.
There should not be so many socket connections (TIME_WAIT means that socket
already closed and waiting for last packages) for three nodes. Could you
please share
-
From: dkarachentsev [mailto:dkarachent...@gridgain.com]
Sent: Tuesday, June 12, 2018 11:37 AM
To: user@ignite.apache.org
Subject: RE: Ignite opens/close 5000 sockets in every 5mins after NODE_FAILED
event
There is no difference on how do you start/stop your node.
Node on start will examine all c
[mailto:dkarachent...@gridgain.com]
Sent: Tuesday, June 12, 2018 11:37 AM
To: user@ignite.apache.org
Subject: RE: Ignite opens/close 5000 sockets in every 5mins after NODE_FAILED
event
There is no difference on how do you start/stop your node.
Node on start will examine all connections specified
killing the
JVM ?
-Original Message-
From: dkarachentsev [mailto:dkarachent...@gridgain.com]
Sent: Tuesday, June 12, 2018 4:58 AM
To: user@ignite.apache.org
Subject: Re: Ignite opens/close 5000 sockets in every 5mins after NODE_FAILED
event
Hi,
TcpDiscoveryMulticastIpFinder produces
Hi,
TcpDiscoveryMulticastIpFinder produces such a big number of connections. I'd
recommend to switch to TcpDiscoveryVmIpFinder with static set of addresses.
Thanks!
-Dmitry
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Hi,
With default configurations in Ignite 1.9,
Netstat shows about 5000 like following logs. And all sockets closes in about 1
min. And this happens in every 5 mins. This behavior started happening ONLY
after a NODE_FAILED event received and we restarted the Ignite(Ignition.stop,
