Skip to main content

Question

 Debraj Bhowmik (DebrajB16819133)
Areteans Technology Solutions
Senior Architect
Areteans Technology Solutions
IN
DebrajB16819133 Member since 2023 22 posts
Areteans Technology Solutions
Posted: May 22, 2023
Last activity: Jul 25, 2023
Posted: 22 May 2023 23:33 EDT
Last activity: 25 Jul 2023 11:53 EDT
Solved

Pega 8.8.2 Multi-node Configuration - Node stuck at status JOINING

In my multi-node horizontal cluster for Pega 8.8.2 in Production there are four different VMs. Pega is running on Postgres 14.6 and Tomcat 9.0.74. I have installed Pega CRM 8.8.2 on top of Pega 8.8.2.

The prconfig.xml has been externalized in all four nodes and it contains the below uncommented lines on all four nodes:

<?xml version="1.0" encoding="UTF-8"?> <pegarules>

    <env name="initialization/settingsource" value="merged" />     <env name="database/databases/PegaRULES/dataSource" value="java:comp/env/jdbc/PegaRULES"/>     <env name="database/databases/PegaDATA/dataSource" value="java:comp/env/jdbc/PegaRULES"/>

</pegarules>  

The -DNodeType JVM argument has not been used for Tomcat.

I serially started the four nodes i.e. after node 1 started I started node 2, after nodes 1 and 2 both started I started node 3, after nodes 1 and 2 and 3 all started I started node 4.

I found that node 4 is getting stuck at JOINING state and it is failing to join the cluster.

I found the below lines in PegaRULES.log file of node 4:

Show More

In my multi-node horizontal cluster for Pega 8.8.2 in Production there are four different VMs. Pega is running on Postgres 14.6 and Tomcat 9.0.74. I have installed Pega CRM 8.8.2 on top of Pega 8.8.2.

The prconfig.xml has been externalized in all four nodes and it contains the below uncommented lines on all four nodes:

<?xml version="1.0" encoding="UTF-8"?> <pegarules>

    <env name="initialization/settingsource" value="merged" />     <env name="database/databases/PegaRULES/dataSource" value="java:comp/env/jdbc/PegaRULES"/>     <env name="database/databases/PegaDATA/dataSource" value="java:comp/env/jdbc/PegaRULES"/>

</pegarules>  

The -DNodeType JVM argument has not been used for Tomcat.

I serially started the four nodes i.e. after node 1 started I started node 2, after nodes 1 and 2 both started I started node 3, after nodes 1 and 2 and 3 all started I started node 4.

I found that node 4 is getting stuck at JOINING state and it is failing to join the cluster.

I found the below lines in PegaRULES.log file of node 4:

                 StreamServer.Default             3e83ff42ac77a65b637f3206485d6709     Proprietary information hidden       NORMAL     (new node)    8.8.2    592ca06f-5f11-4dae-88e9-fed579a17c04  This node ==>    StreamServer.Default             8e12b4684e61afba3b38dc607bceb1ef     Proprietary information hidden       JOINING    (new node)    8.8.2    085fb6b6-ffc9-4594-a995-89810a19464e                   StreamServer.Default             a03ebfbe8b8cdc80eb0a970057a8c09c     Proprietary information hidden       NORMAL     (new node)    8.8.2    825fcc1d-bec7-4b04-a61f-a4235a1805c9                   StreamServer.Default             c5547f532e2244702e2209908c640561     Proprietary information hidden       NORMAL     (new node)    8.8.2    6603bdaf-1896-45e1-a1c8-ce9c4c72bbb0                   pega                             3e83ff42ac77a65b637f3206485d6709     Proprietary information hidden    running    (new node)    8.8.2    67ef89e8-1686-4f12-95fe-09e178dcedaa                   pega                             a03ebfbe8b8cdc80eb0a970057a8c09c     Proprietary information hidden     running    (new node)    8.8.2    577e49a7-26df-44e9-afbe-d755637b00d1                   pega                             c5547f532e2244702e2209908c640561     Proprietary information hidden     running    (new node)    8.8.2    02acec05-9f3d-4c94-9536-5bf6bd9d4332   

Please suggest what needs to be done to resolve this issue.

Please suggest if different node types should be specified for different node through JVM argument.

Show Less
To see attachments, please log in.
Pega Platform 8.8.2
Installation and Deployment
System Administration
Communications and Media
Senior System Architect

  • Reply

Accepted Solution

Posted: 1 year ago
Updated: 1 year ago
Posted: 25 Jul 2023 11:52 EDT
Updated: 25 Jul 2023 11:53 EDT
Debraj Bhowmik (DebrajB16819133)
Areteans Technology Solutions
Senior Architect
Areteans Technology Solutions
IN

@DebrajB16819133

I specified one node as Stream node by adding the JVM argument -DNodeType=Stream. For other three nodes I specified -DNodeType=WebUser,BIX,Search,BackgroundProcessing

I added below lines in prconfig.xml of Stream node:

    <env name="dsm/services/stream/pyUnpackBasePath" value="/pegaenv/kafka" />

    <env name="dsm/services/stream/pyBaseLogPath" value="/pegaenv/kafka- Proprietary information hidden/logs" />

    <env name="dsm/services/stream/pyBrokerAddress" value="I.P. of AS" />

    <env name="dsm/services/stream/pyBrokerPort" value="9092" />

    <env name="dsm/services/stream/pyKeeperPort" value="2181" />

    <env name="dsm/services/stream/pyJmxPort" value="9999" />

    <env name="dsm/services/stream/pyPort" value="7003" />

   

To see attachments, please log in.

We'd prefer it if you saw us at our best.

Pega Collaboration Center has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice