CODEWITHSUNDEEP
ignite
AbNig
AbNig

Reputation: 352

Apache Ignite - Node running on remote machine not discovered

Apache Ignite Version is: 2.1.0

I am using TcpDiscoveryVmIpFinder to configure the nodes in an Apache Ignite cluster to setup a compute grid. Below is my configuration which is nothing but the example-default.xml, edited for the IP addresses:

    <property name="discoverySpi">
        <bean class="org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi">
            <property name="ipFinder">
                <!--
                    Ignite provides several options for automatic discovery that can be used
                    instead os static IP based discovery. For information on all options refer
                    to our documentation: http://apacheignite.readme.io/docs/cluster-config
                -->
                <!-- Uncomment static IP finder to enable static-based discovery of initial nodes. -->
                <!--<bean class="org.apache.ignite.spi.discovery.tcp.ipfinder.vm.TcpDiscoveryVmIpFinder">-->
                <!-- <bean class="org.apache.ignite.spi.discovery.tcp.ipfinder.multicast.TcpDiscoveryMulticastIpFinder">  -->
                <bean class="org.apache.ignite.spi.discovery.tcp.ipfinder.vm.TcpDiscoveryVmIpFinder">
                    <property name="addresses">
                        <list>
                            <!-- In distributed environment, replace with actual host IP address. -->
                            <value>xxx.40.16.yyy:47500..47509</value>
                            <value>xx.40.16.zzz:47500..47509</value>
                        </list>
                    </property>
                </bean>
            </property>
        </bean>
    </property>

If I start multiple nodes on individual machine, the nodes on respective machines discover each other and form a cluster. But, the nodes on the remote machines do not discover each other.

Any advise will be helpful...

Upvotes: 0

Views: 1338

Answers (1)

Evgenii Zhuravlev
Evgenii Zhuravlev

Reputation: 3017

First of all, make sure that you really use this config file and not a default config. With default configuration, nodes can find each other only on the same machine.

Once you've checked it, you also need to test that it's possible to connect from host 106.40.16.64 to 106.40.16.121(and vice versa) via 47500..47509 ports. It's possible that there is a firewall blocked connections or these ports is simply closed.

For example, it's possible to check it with netcat, run this from 106.40.16.64 host:

nc -z 106.40.16.121 47500

Upvotes: 2

Related Questions