You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@ignite.apache.org by gatorjh <ga...@gmail.com> on 2017/04/25 18:55:34 UTC
tcp-disco-ip-finder-cleaner
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.
Re: tcp-disco-ip-finder-cleaner
Posted by Andrey Mashenkov <an...@gmail.com>.
Hi,
Looks like a bug. Here is a ticket [1].
[1] https://issues.apache.org/jira/browse/IGNITE-5117
On Thu, Apr 27, 2017 at 4:01 PM, gatorjh <ga...@gmail.com> wrote:
> Here is the ignite config
>
>
>
>
> --
> View this message in context: http://apache-ignite-users.
> 70518.x6.nabble.com/tcp-disco-ip-finder-cleaner-tp12249p12293.html
> Sent from the Apache Ignite Users mailing list archive at Nabble.com.
>
--
Best regards,
Andrey V. Mashenkov
Re: tcp-disco-ip-finder-cleaner
Posted by gatorjh <ga...@gmail.com>.
Here is the ignite config
--
View this message in context: http://apache-ignite-users.70518.x6.nabble.com/tcp-disco-ip-finder-cleaner-tp12249p12293.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
Re: tcp-disco-ip-finder-cleaner
Posted by Andrey Mashenkov <an...@gmail.com>.
Hi
Would you please share ignite config?
On Tue, Apr 25, 2017 at 9:55 PM, gatorjh <ga...@gmail.com> wrote:
> 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.
>
--
Best regards,
Andrey V. Mashenkov