Posted: 10 Feb 2019 11:56 EST Last activity: 11 Feb 2019 5:58 EST
Agents Node Type Classification - "RunOnAllNodes" - Standard or Advanced Agents
As we have RunOnAllNodes option in Node Type Classification for Agents from PRPC v7.3 to increase the performance by balancing the load across the Nodes in a cluster.
My Question/doubt here is -
1) Does this RunOnAllNodes option is only applicable for Standard agents, As the Standard Agents works on the Queued items. So these items on the queue may be shared across the nodes to balance the load and work faster. Please clarify.
2) Does this RunOnAllNodes option will also be applicable for Advanced Agents also ?
If Yes, How it will handle the load. For example, In the Agent Activity I'm opening the Cases using Obj-Browse/ Report Definition and opening one by one and updating the cases in the list. How it will share the work load if it runs on all nodes. Or this RunOnAllNodes option is only applicable for Standard Agent and this is not applicable for Advanced and Is Advanced Agent should run only on one node, as we have option for Advanced Agents.
Your question is absolutely correct. Standard Agents will handle queued items, till the queue has some items, let it be any no of nodes they will handle till the queue has items. Node classification from 7.3 onwards facilitated to easily identify some of the nodes with a definite name instead of node encrypt code. Pre 7.3 environments used to have schedule data instances on each node, whereas 7.3 onwards we can dedicate particular node as "Background Processing" or "WebUser" which will be running schedule data agents of specific type on specific node only. Whereas "Runonallnodes" is a type of node definition which is all purpose node that schedule data agent can run on any node which of this type. This is as same as pre 7.3 environments. Incase of Advanced agents where the action is recurring or scheduled, which may need to send a report, or notification with a list of results should be a one node action which should not be interfered or repeated by any other node. Load balancing comes in the way as the other advanced agent actions can be handled by other nodes, not picking the ongoing one or sharing the same execution with some other node.