Re: Ignite .NET and TcpDiscoveryStaticIpFinder failure

I created a new VM and it now seems to work ok, I have this message which would indicate everything is connected (which would be correct, 3 nodes, 2 hosts and 6 CPU total) H/N/C [hosts=2, nodes=3, CPUs=6] Also btw, when creating the new VM I had to install Java, I chose jdk-8u221-windows-x64 to m

Re: Ignite .NET and TcpDiscoveryStaticIpFinder failure

Hello! You should make Discovery identical on both nodes, pointing to both nodes via their public address. [11:17:08,959][INFO][tcp-disco-sock-reader-#24][TcpDiscoverySpi] Started serving remote node connection [rmtAddr=/10.0.2.5:53509, rmtPort=53509] [11:17:08,965][INFO][tcp-disco-sock-reader-#2

Re: Ignite .NET and TcpDiscoveryStaticIpFinder failure

I dont know about that, is that maybe because I had both addresses down as endpoints? I have modified app.config on both machines to only point to one another: / 10.0.2.5:47500..47502 /

Re: Ignite .NET and TcpDiscoveryStaticIpFinder failure

Hello! Something is not right here: sockAddrs=[camyakoubCPU/10.0.2.5:47500, /10.0.75.1:47500, /0:0:0:0:0:0:0:1:47500, /127.0.0.1:47500, host.docker.internal/10.0.2.11:47500], Why does node think that it is both 10.0.2.5 and 10.0.2.11? Aren't those supposed to be different addresses? Please provi

Re: Ignite .NET and TcpDiscoveryStaticIpFinder failure

I just realised this is the same situation that is logged here here -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Ignite .NET and TcpDiscoveryStaticIpFinder failure

I am using 2 Azure virtual machines, both part of the same VNET. The network security policy is applied at the network level and allows all traffic in/out from the VNET. I am trying to run a cluster across both machines. Seeing as Azure does not support broadcast I am using a static IP list, which