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

Stale nodes in SMA

SA-56433

Summary



Usecase:

User have 5 nodes in cluster environment and auto-discovery is enabled. All the nodes in the cluster are appeared in System management Application (SMA).

Later, user terminated 2 nodes. Still SMA displays 5 nodes.
 

Error Messages



Not Applicable


Steps to Reproduce



Not Applicable


Root Cause



Auto discovery of nodes in SMA comes from the distributed cluster definition kept in the hazelcast cluster.

If the nodes in the cluster are not synchronized, then it is possible that the node definitions found by SMA can be missing or out of date.

This can happen if not all nodes are restarted and the node that is stopped did not gracefully leave the cluster. In most cases the nodes should enter and leave the cluster and update the cache.

Resolution



Make the following change to the operating environment:
  1. Shut down all the nodes in the cluster.
  2. Truncate pegadata.pr_sys_statusnodes table.
  3. Restart the nodes.

At this point SMA has a consistent and valid view of the cluster.

 

Published August 24, 2018 - 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