Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

Pega nodes crashed due to change in hazelcast cluster membership



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


This issue is scheduled to be resolved in update release Pega 7.2.1
Suggest Edit

Published March 25, 2016 - Updated October 8, 2020

Did you find this content helpful? Yes No

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

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

Pega Community 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
Contact us