Hi, there are two things to check. First, add 47500 port number to all the addresses of your TcpDiscoveryVmIpFinder.addresses property. For instance, 10.0.2.4 needs to be changed to 10.0.2.4:47500.
Second, double-check that every Docker VM exposes the following port numbers - 11211, 47100, 47500, 49112. Those should be exposed by default if an official Ignite image is used. But I would still verify that. - Denis On Thu, Jun 11, 2020 at 11:11 AM risomas <[email protected]> wrote: > Hello, > We have 12 identical azure servers in one network, each 32cpu and 64G ram. > Ignite is running as docker container (identical including config). 8 our > servers are working fine. But 4 are working only sometimes - they cant join > and even worse they are blocking also others. I have recreated these VM > (preserving NIC due licensing of some plugins) but it dint help. Sometimes > these 4 nodes are working fine and they can connect togather, but sometimes > they cant even connect if they are just 2. Identical behavior is while > running as docker-compose or kubernetes. Once servers are connected there > is > no issue they are working fine. > We are using ignite 2.8.1 > > I am attaching logs and config where just 2 servers in the network: > > node8.node8 > <http://apache-ignite-users.70518.x6.nabble.com/file/t2900/node8.node8> > node7.node7 > <http://apache-ignite-users.70518.x6.nabble.com/file/t2900/node7.node7> > both logs are continuing in infinity error loop. > > 2.xml <http://apache-ignite-users.70518.x6.nabble.com/file/t2900/2.xml> > > > > -- > Sent from: http://apache-ignite-users.70518.x6.nabble.com/ >
