Regarding Ingite cluster setup

[Reddy]

Hi All,

 I created two ec2 instances in AWS.In each instance ,Ignite setup has been done and able to start servers.

 below is the configuration in both instances.

First instance not discovering second node and vice versa from console(when I start like ./ignite.sh)

Instance 1:

[11:41:46]
[11:41:46] Security status [authentication=off, tls/ssl=off]
[11:41:48] To start Console Management & Monitoring run ignitevisorcmd.{sh|bat}
[11:41:48]
[11:41:48] Ignite node started OK (id=bd5c353a)
[11:41:48] Topology snapshot [ver=1, servers=1, clients=0, CPUs=1, heap=1.0GB]



Instance 2:
[11:41:46]
[11:41:46] Security status [authentication=off, tls/ssl=off]
[11:41:48] To start Console Management & Monitoring run ignitevisorcmd.{sh|bat}
[11:41:48]
[11:41:48] Ignite node started OK (id=bd5c353a)
[11:41:48] Topology snapshot [ver=1, servers=1, clients=0, CPUs=1, heap=1.0GB]




 <property name="discoverySpi">
            <bean class="org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi">
                <property name="ipFinder">


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

                                <value>10.205.87.20</value>


 would you please advice .

[Denis Magda]

Hi,

Please properly subscribe to the user list (this way we will not have to manually approve your emails). All you need to do is send an email to ì [e-mail]î and follow simple instructions in the reply.

Can each machine see each other using these interfaces below?
10.205.80.41
10.205.87.20

If they can then specify port range to connect to
10.205.80.41:47500..47509
10.205.87.20:47500..47509

This port range is valid if you haven't changed it overriding TcpDiscvoerySpi configuration.

Finally, there is no need to use TcpDiscoveryMulticastIpFinder since multicast is turned off on Amazon.
It makes sense to use TcpDiscoveryVmIpFinder
https://apacheignite.readme.io/docs/cluster-config#static-ip-based-discovery

or event you can switch to AWS IP Finder
https://apacheignite.readme.io/docs/aws-config

or JClouds IP Finder
https://apacheignite.readme.io/docs/generic-cloud-configuration

--
Denis