You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@geode.apache.org by Rajesh Kumar <ra...@gmail.com> on 2020/03/22 17:23:55 UTC

locator is not able to join the distributed system.

Hi All.

   we are using Geode 1.8.0 in peer to peer configuration.

   I am facing a problem where a locator is not able to join the
distributed system.

From the logs I can see that the locator is attempting to join through the
coordinator but it is not able to join. It keeps retrying with the
following message "waiting for a join-response"
Also I have checked the coordinator logs and I see no join request in its
logs. I have checked the ports 41000 and 41001, both of them are open. I
suspect network latency might be the reason but how can I make it resistant
to network latency.

following is the meesage in logs where it tries to join the distributed
system
[info 2020/03/19 16:06:09.312 UTC iHubCacheLocatorProcess_10.248.72.107
<Locator> tid=0x1] Attempting to join the distributed system through
coordinator
10.248.72.106(iHubCacheLocatorProcess_10.248.72.106:14712:locator)<ec><v0>:41000
using address
10.248.72.107(iHubCacheLocatorProcess_10.248.72.107:36893:locator)<ec>:41000


After sometime i see the following in logs where its still waiting for
response
[info 2020/03/19 16:06:19.408 UTC iHubCacheLocatorProcess_10.248.72.107
<Locator> tid=0x1] Probable coordinator is still
10.248.72.106(iHubCacheLocatorProcess_10.248.72.106:14712:locator)<ec><v0>:41000
- waiting for a join-response

Thanks,
Rajesh