Support Article
Pega nodes crashed due to change in hazelcast cluster membership
SA-21311
Summary
Some of Pega nodes fail to initialize after a restart.
Error Messages
“Unable to restart the cluster - Another node is starting and held the lock too long”
“PegaRULES initialization failed. Server: your_server”
Steps to Reproduce
Not Applicable
Root Cause
A defect in Pegasystems’ code or rules. This is due to the race condition issue with hazelcast
Resolution
This issue is scheduled to be resolved in update release Pega 7.2.1
Published March 25, 2016 - Updated October 8, 2020
Have a question? Get answers now.
Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.