Managing decision management nodes
This content applies only to On-premises and Client-managed cloud environments
Manage the decision management nodes in your application by running certain actions for them, for example, repair or clean-up.
- In the header of Dev Studio, click .
- Select the decision management service for which you want to run a selected action by clicking the corresponding tab.
- In the row for a selected DM node, click Execute.
- On the Execute menu, select one of the available actions:
Option Description Start Activates the DM node. The status of the node changes to NORMAL. Stop Deactivates the DM node. The status of the node changes to STOPPED. Repair Removes inconsistencies across all replicas of the data sets in a DM node. Run this operation in the following cases:
- As part of node recovery, when bringing a node back into the cluster after a failure.
- As part of node maintenance, when the node contains data that is not frequently read.
- As part of the node update process, when the node was offline.
Compact Invokes the process in which the Cassandra database combines multiple physical data files on the file system to improve the performance of partition scans and to reclaim space from deleted data. Compaction is a background operation that runs on a regular basis across all nodes in the DM node cluster; however, you can run it explicitly on one DM node by selecting the Compact action. Clean up Removes keys that no longer belong to the DM node. Keys do not belong to a DM node if data was decommissioned, or if the node was rebalanced within the DM node cluster. Decommission Removes the node from the DM node cluster. The data contained in the DM node storage is transferred to other nodes in the DM node cluster.
- Status of decision management nodes
For each decision management node on the Services landing page, the Status column displays the current state of a selected node. Use the following reference information to better understand the status of decision management nodes in your application.
- Status parameters of Decision Data Store nodes (deprecated)
The Decision Data Store (DDS) service stores decision management data in a backing database, such as Cassandra. Use the following reference information to better understand the status parameters of DDS nodes.
- Status parameters of Adaptive Decision Manager nodes
The Adaptive Decision Manager (ADM) creates and updates adaptive models by processing customer responses in real time. By including adaptive models in your next-best-actions strategies, you can make better decisions for your business based on accurately predicted customer behavior. Use the following reference information to better understand the status parameters of ADM nodes.
- Status parameters of Stream nodes
The Stream service enables asynchronous flow of data between processes in Pega Platform. The Stream service is a multinode component that is based on Apache Kafka. Use the following reference information to better understand the status parameters of Stream nodes.
Previous topic Storing customer and analytical data Next topic Status of decision management nodes