Hello! I'm almost certain is that problem is that server node cannot open connection to client node (and while it tries, it will reject connection attempts from client node)
clientReconnectDisabled=true will only concern discovery. In your case, there's no problems with discovery, the problem is with communication (port 47100). Unless discovery fails, node will not be dropped. Regards, -- Ilya Kasnacheev чт, 10 окт. 2019 г. в 08:48, maheshkr76private <maheshk...@gmail.com>: > Ilya. > > What is most mysterious to me is, I disabled reconnect of think client > (clientReconnectDisabled=true). Still the server prints, the below, where > the same thick client is making an immediate attempt to reconnect back to > the cluster, while the previous connecting isn't still successful. > > [00:47:46,004][INFO][grid-nio-worker-tcp-comm-1-#29][TcpCommunicationSpi] > Accepted incoming communication connection [locAddr=/192.168.1.6:47100, > rmtAddr=/192.168.1.71:2007] > *[00:47:46,004][INFO][grid-nio-worker-tcp-comm-1-#29][TcpCommunicationSpi] > Received incoming connection from remote node while connecting to this > node, > rejecting [locNode=3240558e-72b4-4314-a970-0965654e7e6f, locNodeOrder=1, > rmtNode=e1be7b6f-8691-4f81-a03f-c77ff14843ef, rmtNodeOrder=675]* > > This I feel is an internal ignite code logic, which does not seem to be > influenced by the user configuration of IgniteConfiguration params. Can you > cross-check this? My point is, the same node should have to attempt a > reconnect when the user has set clientReconnectDisabled = true in > IgniteConfiguration > > > > -- > Sent from: http://apache-ignite-users.70518.x6.nabble.com/ >
