ADM and Real time data grid node in "LEAVING" status
Hi,
I notice that the ADM and RTDG node are in status "LEAVING". I tried to debug and logs point to error message mentioned below.
If I check the cloud logs and nodes , I am able to verify that the nodes are up and running so there should not be any unresponsive node as such.
| java.lang.IllegalStateException: java.util.concurrent.ExecutionException: com.pega.platform.remoteexecution.management.UnresponsiveNodeException: Remote execution request ea802ece-1f12-4026-bc70-080db72c8d60 was not acknowledged by node 71e0e4c3-9c6e-48bc-9d9a-286545781e36 within the timeout |
Accepted Solution
Updated: 22 Mar 2022 15:06 EDT
Capgemini
IN
Thank you. The issue got resolved after executing the following steps :
- Observe in Admin Studio only one node might be up. "pega_dev_batch" might be down.
- Shutdown all pods
- Truncate the tables below at the database. All tables below are in the Pega Data schema.
- pr_data_stream_nodes
- pr_data_stream_node_updates
- pr_data_stream_sessions
- pr_sys_statusnode
4. Start the pods again and check from Admin Studio if you see 2 nodes or again 1 node.
5. If you still see 1 node as below, please login to the webuser pod via ssh and check if you can telnet port 5701 on the background pod.
Accepted Solution
Updated: 22 Mar 2022 15:06 EDT
Capgemini
IN
Thank you. The issue got resolved after executing the following steps :
- Observe in Admin Studio only one node might be up. "pega_dev_batch" might be down.
- Shutdown all pods
- Truncate the tables below at the database. All tables below are in the Pega Data schema.
- pr_data_stream_nodes
- pr_data_stream_node_updates
- pr_data_stream_sessions
- pr_sys_statusnode
4. Start the pods again and check from Admin Studio if you see 2 nodes or again 1 node.
5. If you still see 1 node as below, please login to the webuser pod via ssh and check if you can telnet port 5701 on the background pod.