Re: tcp-comm-worker-#1 attempt to connect to unrecognized IP addresses

2019-11-10 Thread Ilya Kasnacheev
Hello! There is a known issue with Docker gateway - it is present on all machines, leading Ignite nodes to believe they can reach each other via this interface. Perhaps the same reasoning for other addresses. You can set IgniteConfiguration.localHost or TcpCommunicationSpi.localAddress to the

tcp-comm-worker-#1 attempt to connect to unrecognized IP addresses

2019-11-08 Thread Conrad Mukai (cmukai)
I am running a 4 node ignite cluster in AWS. We are running ignite inside of Docker containers (the image is apacheignite/ignite:2.7.6 from Dockerhub). The container is setup to use the host network. I noticed a lot of warning from the tcp-comm-worker-#1 thread in which it is attempting to