Seperation of responsibility in a Pega Marketing Cluster
For example we have 5 nodes in the cluster, of these i want 1 for use by marketeers, 1 to handle incoming impressions and click throughs, and the other three to run the outbound campaign.
So the emails are set to come into the node made available for incoming traffic, and a url handles the node for the marketeers.
The problem is that the campaign is using all nodes.
However we have created dnodes on all 5 nodes, in Simulation topology we disable 2 nodes from taking part in batch decisioning leaving three enabled with 4 threads on each.
Running like this we find that all five nodes process the campaign so the system is unusable for the marketeers and cant handle incoming responses.
I then change two of the dnodes to be decommisioned (but have not done a restart)
repeating the campaign i still seem to be getting all nodes being used.
What would be the optimum way to configure this so the campaign does not hit nodes we need to isolate for incoming and end users
This is on 7.1.9 of PRPC and 7.14 marketing
thanks
Neil
Accepted Solution
Pegasystems Inc.
GB
If all of the nodes in your environment are part of the DNode cluster there is no separation. DNode functionality is used by both inbound and outbpound processes.
To achieve the separation we need to set the thread count to 0 on the nodes that will be inbound designated nodes.
to achive this Hotfix 27357 was needed as the thread count in simulation topology cannot be set to 0 OOTB.
Once this is set to 0 then those nodes do not take part in the outbound campaign generation and are available for for processing incoming responses and impressions.
Pegasystems Inc.
GB
Hi Neil,
I believe you have an SR-A23452 raised for this issue now. as you have already investigated that setting the thread count to zero in topology landing page prevents the DNode to process in that PRPC system.
However the pzLoadNumberOfThreadsPerNodeInTopology rule involved is a final rule. we have contacted our DSM Subject Matter Experts for this. we will keep you updated vi the SR on the progress.
Thanks
Manu
Accepted Solution
Pegasystems Inc.
GB
If all of the nodes in your environment are part of the DNode cluster there is no separation. DNode functionality is used by both inbound and outbpound processes.
To achieve the separation we need to set the thread count to 0 on the nodes that will be inbound designated nodes.
to achive this Hotfix 27357 was needed as the thread count in simulation topology cannot be set to 0 OOTB.
Once this is set to 0 then those nodes do not take part in the outbound campaign generation and are available for for processing incoming responses and impressions.