TcpCommunicationSpi failed to establish connect to node node will be dropped from cluster.

classic Classic list List threaded Threaded
2 messages Options
sehii sehii
Reply | Threaded
Open this post in threaded view
|

TcpCommunicationSpi failed to establish connect to node node will be dropped from cluster.

This post was updated on .
I have a question.

our company system uses Ignite1.9  version.

we made the topology with 8 nodes.(01-08)

In our business logic, every one minute all nodes have to check other nodes
status each other by Ignite ping .

when 02_node sent ignite ping to the 06_node, the exception was occured.
Exception is related timeout

That  is exception log.

==================
2018-12-29 05:59:09.163[WARN ] [MonitoringManager : TCheckStatus]
[TcpCommunicationSpi]
TcpCommunicationSpi failed to establish connect to node node will be dropped
from cluster
  [rmtNode=TcpDiscoveryNode[id=a5a3dd09-ba72-42be-b3cc-644ca282b4b0
  , addrs=[x.x.x.x2]
  ,sockAddrs=[/x.x.x.x2:xx301]
  ,discPort=17301
  ,order=5
  ,intOrder=5
  ,lastExchangeTime=1544663946652
  ,loc=false,ver=1.9.0# 20170302-sha1:a8169da
  , isClient=false]err=class o.a.i.IgniteCheckedException: Failed to connect
to node ( is node still alive?)

Make sure that each ComputeTask and
cache Transaction has a timeout set in order to prevent parties from waiting
forever in case of network issue [
nodeId=a5a3dd09-ba72-42be-b3cc-644ca282b4b0
, addrs=[/x.x.x.x2:xx301]]
,connectErrs=[class o.a.i.IgniteCheckedException: Failed to connect to
address


can you help me??

I want to know what i have to do , what i have to check.






--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Stanislav Lukyanov Stanislav Lukyanov
Reply | Threaded
Open this post in threaded view
|

RE: TcpCommunicationSpi failed to establish connect to node node will bedropped from cluster.

Well, it means that node 6 didn’t answer to the node 2.

Was the node 6 dropped from the cluster after that?

 

It could happen because of a network issue, GC on the node 6, perhaps some OS/VM issue.

Can’t say anything more specific with that little info.

 

Stan

 

From: [hidden email]
Sent: 4 января 2019 г. 7:45
To: [hidden email]
Subject: TcpCommunicationSpi failed to establish connect to node node will bedropped from cluster.

 

I have a question.

 

our company system uses Ignite1.9  version.

 

we made the topology with 8 nodes.(01-08)

 

In our business logic, every one minute all nodes have to check other nodes

status each other by Ignite ping .

 

when 02_node sent ignite ping to the 06_node, the exception was occured.

Exception is related timeout

 

That  is exception log.

 

==================

2018-12-29 05:59:09.163[WARN ] [MonitoringManager : TCheckStatus]

[TcpCommunicationSpi]

TcpCommunicationSpi failed to establish connect to node node will be dropped

from cluster

  [rmtNode=TcpDiscoveryNode[id=a5a3dd09-ba72-42be-b3cc-644ca282b4b0

  , addrs=[x.x.x.x2]

  ,sockAddrs=[/x.x.x.x2:17301]

  ,discPort=17301

  ,order=5

  ,intOrder=5

  ,lastExchangeTime=1544663946652

  ,loc=false,ver=1.9.0# 20170302-sha1:a8169da

  , isClient=false]err=class o.a.i.IgniteCheckedException: Failed to connect

to node ( is node still alive?)

 

Make sure that each ComputeTask and

cache Transaction has a timeout set in order to prevent parties from waiting

forever in case of network issue [

nodeId=a5a3dd09-ba72-42be-b3cc-644ca282b4b0

, addrs=[/172.31.13.52:18301]]

,connectErrs=[class o.a.i.IgniteCheckedException: Failed to connect to

address

 

 

can you help me??

 

I want to know what i have to do , what i have to check.

 

 

 

 

 

 

--

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