Most likely you need to get them aware of each other. I.e. configure DiscoverySpi addresses range to 49500..49509.
Please, share you Ignite config for containerized nodes. Alexandr From: vitalys Sent: Thursday, August 8, 2019 9:00 PM To: [email protected] Subject: RE: Running Ignite Cluster using Docker containers Here is the problem. I can start one Server Node in the Docker container and I can connect to that Node from my client application. However When I run another Docker Containers they are not joining the Cluster. Here is an example : Node 1 : docker run --rm --name myignite1 -p 47501:47500 -p 47101:47100 -p 10801:10800 -it myignite/ignite:1.0 [17:50:48] Topology snapshot [ver=1, locNode=d290d944, servers=1, clients=0, state=INACTIVE, CPUs=2, offheap=0.39GB, heap=0.43GB] Node 2 : docker run --rm --name myignite3 -p 47503:47500 -p 47103:47100 -p 10803:10800 -it myignite/ignite:1.0 [17:54:22] Topology snapshot [ver=1, locNode=fe47c5c7, servers=1, clients=0, state=INACTIVE, CPUs=2, offheap=0.39GB, heap=0.43GB] ________________________________________________________________________________ They Nodes can't discover one another. When I am starting my Nodes there is no such issue since they are using the same Configuration where TcpDiscoveryIpVmFimder is defined : <bean class="org.apache.ignite.spi.discovery.tcp.ipfinder.vm.TcpDiscoveryVmIpFinder"> <property name="addresses"> <list> <value>localhost:47500..47504</value> </list> </property> </bean> So my question is : how do I make multiple nodes running in different Docker Containers discover each other? -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/
