ignite-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Yakov Zhdanov <yzhda...@apache.org>
Subject Re: Not able to join cluster with Zookeeper based IP finder
Date Wed, 07 Dec 2016 06:07:37 GMT
for some reason these two nodes register themselves with incorrect
addresses or, to be more exact, incorrect ports - 47101 instead of 47500.
Then they both get 2 addresses (1st is own address, 2nd is address for
remote node) but cannot connect to them since port is incorrect.

2016-12-06 16:00:25,218 - INFO --- [main]
.s.d.t.i.z.TcpDiscoveryZookeeperIpFinder : Registering addresses with
ZooKeeper IP Finder:
[ip-10-204-68-205.ec2.internal/10.204.68.205:47101]
2016-12-06 16:00:25,372 - INFO --- [main]
.s.d.t.i.z.TcpDiscoveryZookeeperIpFinder : ZooKeeper IP Finder
resolved addresses: [/10.204.69.145:47101, /10.204.68.205:47101]

This may happen if you have address resolver configured on these two nodes.
Please provide configuration for those nodes.

--Yakov

2016-12-06 23:27 GMT+07:00 ghughal <bakul.ghughal@gmail.com>:

> I removed 3rd client node from cluster as it's not relevant for this issue.
> Here's logs for both nodes with quiet mode set to false:
>
> node1.log
> <http://apache-ignite-users.70518.x6.nabble.com/file/n9421/node1.log>
> node2.log
> <http://apache-ignite-users.70518.x6.nabble.com/file/n9421/node2.log>
>
>
>
> --
> View this message in context: http://apache-ignite-users.
> 70518.x6.nabble.com/Not-able-to-join-cluster-with-
> Zookeeper-based-IP-finder-tp9311p9421.html
> Sent from the Apache Ignite Users mailing list archive at Nabble.com.
>

Mime
View raw message