(Ignite ver: 2.6)Failing client node due to not receiving metrics updates from client node

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

(Ignite ver: 2.6)Failing client node due to not receiving metrics updates from client node

I am using ignite 2.6 version.  

Ignite client node is failing in prod env giving following warning. 
So I changed the  clientFailureDetectionTimeout to 90000 millis. But this did not solve the problem. I am still facing this issue.

1) Can someone please explain the reason for this issue?  Is it really happening because of network issue or there could be some other reason for this?

Also I see one issue logged for this https://issues.apache.org/jira/browse/IGNITE-10354.

2) This is fixed in ignite 2.8 version. Will upgrading to Ignite 2.9.1 solve this issue?

2021-02-16 07:56:10,874 70815632 [tcp-disco-msg-worker-#2%springDataNode%] WARN  o.a.i.s.d.tcp.TcpDiscoverySpi - Failing client node due to not receiving metrics updates from client node within 'IgniteConfiguration.clientFailureDetectionTimeout' (consider increasing configuration property) [timeout=60000, node=TcpDiscoveryNode [id=7b0d1b78-004b-465a-8dcd-de706cbd4e8e, addrs=[0:0:0:0:0:0:0:1%lo, 127.0.0.1, 1.1.17.224], sockAddrs=[host03.com, /0:0:0:0:0:0:0:1%lo:0, /127.0.0.1:0], discPort=0, order=34, intOrder=22, lastExchangeTime=1613461171898, loc=false, ver=2.6.0#20180710-sha1:669feacc, isClient=true]]
stephendarlington stephendarlington
Reply | Threaded
Open this post in threaded view
|

Re: (Ignite ver: 2.6)Failing client node due to not receiving metrics updates from client node

What does it say on the client side? If it’s a network issue, there are at least two parties and we can’t be sure what’s happen just by looking at one side.

Sometimes it’s genuinely a network issue. Other times it’s a long JVM pause. Others it’s a bug, like the one you identified.

Regards,
Stephen

On 16 Feb 2021, at 12:09, Prasad Bhalerao <[hidden email]> wrote:

I am using ignite 2.6 version.  

Ignite client node is failing in prod env giving following warning. 
So I changed the  clientFailureDetectionTimeout to 90000 millis. But this did not solve the problem. I am still facing this issue.

1) Can someone please explain the reason for this issue?  Is it really happening because of network issue or there could be some other reason for this?

Also I see one issue logged for this https://issues.apache.org/jira/browse/IGNITE-10354.

2) This is fixed in ignite 2.8 version. Will upgrading to Ignite 2.9.1 solve this issue?

2021-02-16 07:56:10,874 70815632 [tcp-disco-msg-worker-#2%springDataNode%] WARN  o.a.i.s.d.tcp.TcpDiscoverySpi - Failing client node due to not receiving metrics updates from client node within 'IgniteConfiguration.clientFailureDetectionTimeout' (consider increasing configuration property) [timeout=60000, node=TcpDiscoveryNode [id=7b0d1b78-004b-465a-8dcd-de706cbd4e8e, addrs=[0:0:0:0:0:0:0:1%lo, 127.0.0.1, 1.1.17.224], sockAddrs=[host03.com, /0:0:0:0:0:0:0:1%lo:0, /127.0.0.1:0], discPort=0, order=34, intOrder=22, lastExchangeTime=1613461171898, loc=false, ver=2.6.0#20180710-sha1:669feacc, isClient=true]]