Question
Common Wealth Bank of Australia
AU
Last activity: 16 Oct 2018 12:03 EDT
Unable to add second node to the search index host node setting
Hi ,
Our application infra has a single active node & a stand by node (though Pega is running it is not added to the load balancer) which will get rolled over automatically when the active node goes down.With this landscape when i try to add the stand by node as a second search index host node, the system throws the error message "•** Unable to add 14E37A38BD13BF5206630FEE as indexing node; It seems to be offline. Please verify the nodeID specified". Any help in resolving the above issue will be highly appreciated.
Also there is no proper documentation for multinode search configuration (Exact steps involved in configuring from DSS to the search landing page settings) for Pega 7.2.
**Moderation Team has archived post**
This post has been archived for educational purposes. Contents and links will no longer be updated. If you have the same/similar question, please write a new post.
Accepted Solution
Common Wealth Bank of Australia
AU
Hi ManjuPai,
Please check in your prconfig.xml if you have the below setting for hazelcast clustering
<env name="cluster/hazelcast/multicast/enabled" value="false"/>
<env name="cluster/hazelcast/members" value="host name of node 1"/>
if yes, try removing them.
The above fix resolved my issue
JPMorgan Chase & Company
US
Hi,
Could you please let us know where this error printed, is it in pega rules log ?, seems to be load balancer not able identify the Node id which you had configured.
Pegasystems Inc.
US
Are both nodes able to communicate with each other for search (default ports 9300-9400) and for cluster communication (default ports 5700-5800)? If you check the pr_sys_statusnodes table, does it show the "standby" node as being something other than online?
I would guess the issue is one of the above. As far as multinode search configuration, there isn't anything else to do other than adding the additional nodes after the first has finished building the initial indexes.
Pai G
IN
hi,
We too have similar issue in our environment where we have 3 nodes. In pr_sys_statusnodes table, where do we need to check if its showing as "Standby" node. I did not find this value in any of the column.
Techmahindra
IN
Hello Manjunath,
Please refer to the pr_sys_statusnodes column pyRunState column for the nodes that are present there. May be you can send screen shot as well
Regards,
Shanthini Charles
Virtusa IT Consulting
AE
Hi,
Please check if you have the similar behaviour as described in this article https://community.pega.com/support/support-articles/unable-add-index-node
If yes, please try the solution as mentioned in the article.
Thanks!
Accepted Solution
Common Wealth Bank of Australia
AU
Hi ManjuPai,
Please check in your prconfig.xml if you have the below setting for hazelcast clustering
<env name="cluster/hazelcast/multicast/enabled" value="false"/>
<env name="cluster/hazelcast/members" value="host name of node 1"/>
if yes, try removing them.
The above fix resolved my issue