Getting node ping failures since Ignite 2.11.1

[Thomas Kramer <do...@gmx.de>]

Hi,

with testing to switch from Ignite 2.8.1 to 2.11.1 I'm getting constant
warnings in log now like this:

*/WARN TcpDiscoverySpi                          Failed to ping node
[nodeId=null]. Was unable to open the socket at all. Cause: Connection
refused/*

It seems to happen in IpFinderCleaner which calls pingNode(addr, null,
null).

And it calls it with 127.0.0.1:47500 as you can see in screenshot below.
This wasn't visible in Ignite 2.8.1.

Why is this warning happening now?

Thanks!

Re: Getting node ping failures since Ignite 2.11.1

[do...@gmx.de]

I think I found the reason why this is happening. It's happening on a
server node that shall run on its own. However, I still had a discovery
spi for localhost/127.0.0.1. This didn't seem to be an issue (show a
warning) in 2.8.1 but now it does. So I fixed it in my server config.


On 27.12.21 19:57, Thomas Kramer wrote:
>
> Hi,
>
> with testing to switch from Ignite 2.8.1 to 2.11.1 I'm getting
> constant warnings in log now like this:
>
> */WARN TcpDiscoverySpi                          Failed to ping node
> [nodeId=null]. Was unable to open the socket at all. Cause: Connection
> refused/*
>
> It seems to happen in IpFinderCleaner which calls pingNode(addr, null,
> null).
>
> And it calls it with 127.0.0.1:47500 as you can see in screenshot
> below. This wasn't visible in Ignite 2.8.1.
>
> Why is this warning happening now?
>
> Thanks!
>
>