Question
Pega nodes are not seen in cluster management
Hello. I've got pega cluster with 5 separated nodes and 4 nodes of it are not visible in "Cluster management" tab but they exist in "System Node" tab. If i manually set in prconfig options:
<env name="identification/cluster/protocol" value="Hazelcast" />
<env name="cluster/Hazelcast/interface" value="IP address of this node" />
<env name="cluster/Hazelcast/ports" value="port range" />
<env name="cluster/Hazelcast/members" value="members IP of the clusters" />
<env name="indexing/distributed/network/host" value="IP address of this node" />
for each of them my problem dissapear and all nodes become visible. What should i check/do to solve this problem without editing prconfig ?
Without manual configuration all of nodes are using 192.168.122.1 ip-adress.
I am new to PEGA. I can see the same issue. I don't see all nodes in cluter management and I have cleared the statusnodes tables. How to configure through DSS. Could you please help me out?
thanks
Hey. Just add on each node in procnfig file this line, replacing with your ip-adresses: <env name="cluster/Hazelcast/members" value="10.68.213.234,10.116.9.96,10.116.9.97,10.116.9.98,10.116.9.99" />
One of my environment using ignite. 3 node ignite cluster.
In Ingite Server - prconfig.xml (prcluster_service.war)
<env name="identification/cluster/protocol" value="ignite" />
<env name="identification/cluster/public/address" value="XXXX-ignite server IP" />
And on Pega Node:
- Added below lines to prcofig.xml (prweb/web-inf/classes) to enable to client mode.
<env name="cluster/clientserver/clientmode" value="true" />
<env name="identification/cluster/protocol" value="ignite" />
- Restarted the Tomcat
--- My Question is - As I have 3 Ignite Servers, Can I mention three Node IPs like below for prconfig.xml (prcluster_service)
Will below entry work for Ignite also?
Ex : <env name="cluster/ignite/members" value="10.68.213.234,10.116.9.96,10.116.9.97,10.116.9.98,10.116.9.99" />
Thanks
Hi,
Have you tried clearing the entries in pr_sys_statusnodes and start nodes one by one.