Status of decision data nodes
For each decision data node on the Services landing page, the Status column shows the current state of that decision data node. Use the following reference information to better understand the status of decision data nodes in your application.
- JOINING
- The node is in the process of being enabled, and the server is joining the decision data node cluster.
- NORMAL
- The decision data node is in a normal, functional state.
- STOPPED
- The node is deactivated but is still recognized as a decision data node.
- LEAVING
- The node is in the process of being decommissioned, and the server is leaving the decision data node cluster.
- MOVING
- The node is in the process of being moved to a new position in the decision data cluster ring.
- CORRUPTED
- The file system in the decision data node is corrupted. Use a repair operation to make this decision data node operational again.
- REPAIRING
- A repair operation is running on the decision data node.
- COMPACTING
- A compact operation is running on the decision data node.
- CLEARING
- A cleanup operation is running on the decision data node.
- UNKNOWN
- The status of the decision data node is currently unknown.
Each node takes a payload that is relative to the number of available nodes. Cassandra balances the payload (data ownership) across the nodes and the total ownership adds up to 100%. For example, in a cluster consisting of three nodes, each node has ownership of approximately 33% of the data. However, balancing the payload might not be performed correctly if there are networking issues in the process of nodes joining the cluster. For this reason, Pega Platform allows one node to join at a time. The remaining nodes stay in pending joining until the previous node finishes joining.