You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@ignite.apache.org by Skollur <Sk...@idbny.com> on 2018/09/05 16:44:50 UTC

Igniter TCPDiscovery

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.169.15.51) and mismatch while loading the data. How this is
possible when I had code as below?

        TcpDiscoverySpi discovery = new TcpDiscoverySpi();
       TcpDiscoveryMulticastIpFinder ipFinder = new
TcpDiscoveryMulticastIpFinder();
      
ipFinder.setAddresses(Arrays.asList("127.0.0.1:10800,93.169.15.50")));
       discovery.setIpFinder(ipFinder);
       cfg.setDiscoverySpi(discovery);
       cfg.setPeerClassLoadingEnabled(true);






--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Igniter TCPDiscovery

Posted by Denis Magda <dm...@apache.org>.
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 <Sk...@idbny.com> wrote:

> 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.169.15.51) and mismatch while loading the data. How this is
> possible when I had code as below?
>
>         TcpDiscoverySpi discovery = new TcpDiscoverySpi();
>        TcpDiscoveryMulticastIpFinder ipFinder = new
> TcpDiscoveryMulticastIpFinder();
>
> ipFinder.setAddresses(Arrays.asList("127.0.0.1:10800,93.169.15.50")));
>        discovery.setIpFinder(ipFinder);
>        cfg.setDiscoverySpi(discovery);
>        cfg.setPeerClassLoadingEnabled(true);
>
>
>
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>

Re: Igniter TCPDiscovery

Posted by akurbanov <an...@gmail.com>.
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 adresses in ip finder:

<bean
class="org.apache.ignite.spi.discovery.tcp.ipfinder.multicast.TcpDiscoveryMulticastIpFinder">
    <property name="multicastGroup" value="228.11.11.158"/>
</bean>

Regards,




--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/