We are running Ignite 1.8.0 within Docker on an AWS instance. Ignite registers with Zookeeper. We use a BasicAddressResolver in the Ignite config so that only the Docker host IP is registered. This works fine until the tcp-disco-ip-finder-cleaner thread kicks in and adds the loopback and the Docker host IP addresses to the address list.
#startup looks good #first time from thread looks good #Bam! Loopback and container IP now in the list. What could I be doing wrong? Any help appreciated. -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/tcp-disco-ip-finder-cleaner-tp12249.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.
