Re: Igniter TCPDiscovery

2018-09-07 Thread Denis Magda
That's because they found each other via the multicast protocol - you're using TcpDiscoveryMulticastIpFinder Replace it with the static IP finder listing the IPs there: https://apacheignite.readme.io/docs/tcpip-discovery#section-static-ip-finder -- Denis On Wed, Sep 5, 2018 at 9:44 AM Skollur w

Re: Igniter TCPDiscovery

2018-09-05 Thread akurbanov
Hello, I would recommend you to use org.apache.ignite.spi.discovery.tcp.ipfinder.vm.TcpDiscoveryVmIpFinder for this needs. Is there any specific reason for binding server node to loopback address? Another option is to define different multicastGroup for your current implementation and get rid of

Igniter TCPDiscovery

2018-09-05 Thread Skollur
I have two independent machines where ignite server node is running. i.e ,193.169.15.50 and ,193.169.15.51. Both are running with two different versions of cache. However when i tried to load the data to cache(i.e ,193.169.15.50) from one of these machine, it always finds another machine (i.e 193.