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

Production Load Balancer down and one node down with exceptions



There are hazelcast communication error messages in the logs for every second and logs are growing at rapid phase. One of the node in production is down.

Error Messages

Error 503: PegaRULES server not available while launching the URL.

Following is the repetitive error from Node 2 sysout.log which is happening every few milliseconds:

[12/15/16 16:37:34:911 CET] 00000098 InternalParti W com.hazelcast.partition.InternalPartitionService [node2]:5701 [6971d459d3c43fe825c043f7e6116d77] [3.4.1] Following unknown addresses are found in partition table sent from master[Address[node1]:5701]. (Probably they have recently joined or left the cluster.) {
Address[DR Node1]:5701
Address[DR Node 2]:5701


Steps to Reproduce

Not applicable

Root Cause

A defect or configuration issue in the operating environment. 

There was no communication between production nodes and DR nodes. DR nodes are not used in this environment.


Here’s the explanation for the reported behavior: 

There was no communication between production nodes and DR nodes, shutdown the DR nodes to address the hazelcast errors.

Restarting the problematic node resolves the issue.


Published December 21, 2016 - Updated October 8, 2020

Was this useful?

0% found this useful

Have a question? Get answers now.

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

Did you find this content helpful?

Want to help us improve this content?

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