You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@ignite.apache.org by Akash Shinde <ak...@gmail.com> on 2021/06/10 05:09:54 UTC
Failing client node due to not receiving metrics updates-IGNITE-10354
Hi, There is a cluster of four server nodes and six client nodes in
production. I was using ignite 2.6.0 version and all six client nodes were
failing with below error
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=90000, node=TcpDiscoveryNode
[id=12f9809d-95be-47e3-81fe-d7ffcaab064c,
consistentId=12f9809d-95be-47e3-81fe-d7ffcaab064c, addrs=ArrayList
[0:0:0:0:0:0:0:1%lo, 127.0.0.1, <IP>], sockAddrs=HashSet
[/0:0:0:0:0:0:0:1%lo:0, /127.0.0.1:0, <failing node address>/<ip>:0],
discPort=0, order=155, intOrder=82, lastExchangeTime=1623154238808,
loc=false, ver=2.10.0#20210310-sha1:bc24f6ba, isClient=true]]
Then I have upgraded the ignite version to 2.10.0 to get the fix of known
issue IGNITE-10354 <https://issues.apache.org/jira/browse/IGNITE-10354>.
But I am still facing the issue even after upgrading to the 10.2.0
ignite version.
Could someone help here.
Thanks,
Akash
Re: Failing client node due to not receiving metrics updates-IGNITE-10354
Posted by Akash Shinde <ak...@gmail.com>.
Hi Zhenya, Thanks for the quick response.
I am checking with the network team as well for any network glitch
occurrence.
Thanks,
Akash
On Thu, Jun 10, 2021 at 1:06 PM Zhenya Stanilovsky <ar...@mail.ru>
wrote:
> Hello Akash !
> I found that fix mentioned by you is ok.
> Why do you think that your network between server and client is ok ?
> Can you add some network monitoring here ?
> thanks.
>
>
>
>
>
>
> Hi, There is a cluster of four server nodes and six client nodes in
> production. I was using ignite 2.6.0 version and all six client nodes were
> failing with below error
>
> 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=90000, node=TcpDiscoveryNode
> [id=12f9809d-95be-47e3-81fe-d7ffcaab064c,
> consistentId=12f9809d-95be-47e3-81fe-d7ffcaab064c, addrs=ArrayList
> [0:0:0:0:0:0:0:1%lo, 127.0.0.1, <IP>], sockAddrs=HashSet
> [/0:0:0:0:0:0:0:1%lo:0, /127.0.0.1:0, <failing node address>/<ip>:0],
> discPort=0, order=155, intOrder=82, lastExchangeTime=1623154238808,
> loc=false, ver=2.10.0#20210310-sha1:bc24f6ba, isClient=true]]
>
> Then I have upgraded the ignite version to 2.10.0 to get the fix of known
> issue IGNITE-10354 <https://issues.apache.org/jira/browse/IGNITE-10354>.
> But I am still facing the issue even after upgrading to the 10.2.0
> ignite version.
>
> Could someone help here.
>
> Thanks,
> Akash
>
>
>
>
>
>
>
>
Re: Failing client node due to not receiving metrics updates-IGNITE-10354
Posted by Zhenya Stanilovsky <ar...@mail.ru>.
Hello Akash !
I found that fix mentioned by you is ok.
Why do you think that your network between server and client is ok ?
Can you add some network monitoring here ?
thanks.
>
>>
>>>Hi, There is a cluster of four server nodes and six client nodes in production. I was using ignite 2.6.0 version and all six client nodes were failing with below error
>>>
>>>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=90000, node=TcpDiscoveryNode [id=12f9809d-95be-47e3-81fe-d7ffcaab064c, consistentId=12f9809d-95be-47e3-81fe-d7ffcaab064c, addrs=ArrayList [0:0:0:0:0:0:0:1%lo, 127.0.0.1, <IP>], sockAddrs=HashSet [/0:0:0:0:0:0:0:1%lo:0, / 127.0.0.1:0 , <failing node address>/<ip>:0], discPort=0, order=155, intOrder=82, lastExchangeTime=1623154238808, loc=false, ver=2.10.0#20210310-sha1:bc24f6ba, isClient=true]]
>>>
>>>Then I have upgraded the ignite version to 2.10.0 to get the fix of known issue IGNITE-10354 . But I am still facing the issue even after upgrading to the 10.2.0 ignite version.
>>>
>>>Could someone help here.
>>>
>>>Thanks,
>>>Akash
>>>
>>
>>
>>
>>