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

Servers fail with ClusterAvailabilityException



Servers fail with ClusterAvailabilityException.

Error Messages

Caused by: pega.decision.vbd.node.ClusterAvailabilityException: No cluster nodes available
at pega.decision.vbd.node.client.ServerNodeCache.getNext([vbd-node-jar:?]
at pega.decision.vbd.node.client.DefaultClientClusterExecutor.execute( ~[vbd-node-jar:?]
at pega.decision.vbd.node.client.ClientEngine.insert([vbd-node-jar:?]
at pega.decision.vbd.service.impl.VBDServiceImpl.insertFactRecords([vbd-impl-jar:?]

Steps to Reproduce


Root Cause

The cluster crashes and the nodes stop communicating. Since the nodes do not receive signal from the other nodes (old node is terminated), they consider that they are broken and cast the members away.


Here’s the explanation for the reported behavior: 
According to the architecture, the existing node is replaced by a new node if any of the following occurs:   
  • High resource utilization and the node enters the hung state
  • Application requires a longer time to open due to any activity
  • Abnormalities in the server

A JAR file which requires a server restart to reflect is imported. Error message displays after the server restart since the nodes are unavailable to form a cluster. However, the server is stable after it receives the heartbeat message from a new node.


Published 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