ignite-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Alexandr Shapkin <lexw...@gmail.com>
Subject RE: Running Ignite Cluster using Docker containers
Date Thu, 08 Aug 2019 11:10:44 GMT

Please, refer to the docker port forwarding documentation [1]
In other words, instead of  -p 47503:47503 you need to write -p 47503:47500, 
unless you have not configured the default discovery spi port to 47503 explicitly.

Please, recall that Ignite requires a minimum set of open ports for a general communication:
TcpDiscoverySpi port - 47500 and TcpCommunicationSpi port - 47100.

If you want to enable a thin clients communication, then 10800 default port is required as

To summarize, your docker cmd should look like:
docker run --rm --name myignite1 -p 47503:47500 -p 47103:47100 -p 10803:10800 -it ignite-image

Now your host machine should be able to connect to the container with 47103, 47503, 10803

[1] - https://docs.docker.com/config/containers/container-networking/#published-ports

From: vitalys
Sent: Wednesday, August 7, 2019 6:11 PM
To: user@ignite.apache.org
Subject: RE: Running Ignite Cluster using Docker containers

I am getting different issue now. I configured my Ignite Server to use Unicast : 

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

When I start my first Docker Container it looks good and I am able to connect to the Ignite
Server using my client code. 

 docker run --rm --name myignite1 -p 47500:47500 -p 47501:47501 -p 10800:10800 -it myignite/ignite:1.0 

However when I am trying to bring up another server Node : 

 docker run --rm --name myignite2 -p 47502:47502 -p 47503:47503 -p 10801:10800 -it myignite/ignite:1.0 

it's not forming a Cluster with the previously started Node. 

If I run my Ignite Docker image like that : 

 docker run --rm --net=host --name myignite2 -p 47502:47502 -p 47503:47503 -p 10801:10800
-it myignite/ignite:1.0 

 then Cluster is created and I can see it if I open "ignitevisor" console. However Client
application is unable to join the Cluster then 
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
View raw message