ignite-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Yakov Zhdanov <yzhda...@gridgain.com>
Subject Re: Not able to join cluster with Zookeeper based IP finder
Date Thu, 08 Dec 2016 07:10:07 GMT
I think it can work fine if along with incorrect addresses node also get
correct (means address that is listened to by Ignite on some host)
addresses on start.

AddressResolver should be used if you want to build topology having
different parts of it behind NAT, for example. If it is plain network, then
remove it, since it is misuse.

Ignite automatically picks unused port and propagates this info to the rest
of the cluster.

Yakov Zhdanov, Director R&D
*GridGain Systems*

2016-12-08 5:03 GMT+07:00 ghughal <bakul.ghughal@gmail.com>:

> Yakov,
> We are configuring 47101 port for external address resolver. I provided
> code
> we use to configure ignite node in my original post. Essentially for one of
> the node it will be like this: (port 47101 is just one port we chose as it
> was one of unused port)
> Are you suggesting if we use address resolver, we need to use port 47500 or
> make sure ignite binds to the port we use for address resolver?
> Also, this issue seem to be happening only when we start both node at same
> time. If we start nodes one by one, it works fine.
> --
> View this message in context: http://apache-ignite-users.
> 70518.x6.nabble.com/Not-able-to-join-cluster-with-
> Zookeeper-based-IP-finder-tp9311p9439.html
> Sent from the Apache Ignite Users mailing list archive at Nabble.com.

View raw message