Question
TATA Consultancy Services
IN
Last activity: 5 Dec 2017 23:59 EST
Nodes not communicating to other nodes in Search Landing page
Hi,
I have 20 nodes in production. I am unable to add search node configuration in the slave node at search landing page. The master node showing offline in slave node search index page itself. We are getting below mentioned Error on the node startup.
Node could not join cluster at node: xxx.xx.xxx.xxAddress Cause: the target cluster has a different group-name [cluster]
Address xx.xx.xx.xx is added to the blacklist.
Please advise.
Regards,
Muthu
***Edited by Moderator Marissa to update categories***
Accepted Solution
Pegasystems Inc.
US
This indicates a hazelcast communication problem. If your servers have more than one network card, you may need to add the following prconfig setting on each node so they know where they should be listening for hazelcast communications:
<env name="cluster/hazelcast/interface" value="xx.xx.xx.xx"/>
The value should be the IP on the network card that should be used for Pega node communications (will vary from server to server in a cluster).
This indicates a hazelcast communication problem. If your servers have more than one network card, you may need to add the following prconfig setting on each node so they know where they should be listening for hazelcast communications:
<env name="cluster/hazelcast/interface" value="xx.xx.xx.xx"/>
The value should be the IP on the network card that should be used for Pega node communications (will vary from server to server in a cluster).
Ports 5701-5800 are used by default for this and should be open. The ports used can be adjusted with the following setting:
<env name="cluster/hazelcast/ports" value="xxxx-xxxx" />
If you just started seeing this issue, it was likely due to a recent network change.