Unable to separate inbound and outbound campaign traffic
There are eight nodes in a cluster. Out of which five are allotted for outbound campaign, one for marketers to run reports, and two to handle inbound impressions, click-through learnings, and so on. The eight nodes are defined as DNodes. The work is distributed among all nodes if they are in the DNode cluster.
This affects the performance of two nodes for inbound impression and click-through processing. The inbound nodes are unable to handle inbound traffic as they are too busy processing the outbound campaign.
Steps to Reproduce
- Run a distributed campaign across minimum three nodes.
- Define all PRPC nodes as in a DNode cluster.
- In simulation topology, enable two nodes for batch decisioning or distributed batch.
A defect in Pegasystems’ code or rules. It is a default behavior of DNode functionality to utilize all nodes in cluster to distribute the work. The processing on a node can be prevented by setting the Thread count in the Decisioning Simulation Topology landing page for the nodes that must be excluded in DNode processing. However, there is no facility to set the count to zero in the User Interface (UI).
Note: Additional Steps
- After applying the hotfix, navigate to Designer Studio > Decisioning > Infrastructure > Simulation Settings > Topology (the Topology landing page) for every node in the PRPC cluster. The Threads' list will start from zero even in case of disabled agents.
- Set Threads to zero for those nodes that must be excluded from DNode processing.