Agent does not run on multiple nodes
After modifying the Node classification, agent processing that occurred on multiple nodes only processes on a single node.
Steps to Reproduce
Queue multiple work objects for processing through an agent.
A defect or configuration issue in the operating environment.
The agent performing the processing was not associated with all the node types it was intended to run on.
Perform the following local-change to associate the agent with the desired node types:
Click Designer Studio > System > Operations > Node Classification.
On the Agents tab, click +New association for the agent to which a node type must be added.
Select a node type from the list. The agent runs for all the nodes that are started with the node types associated with the agent, including the node type that is added.
RunOnAllNodes – The agent runs on all the nodes in the cluster that are started with any node type, regardless of the node classification.
Search – The agent runs on a search node for search jobs.
WebUser – The agent runs on a web user node for web user jobs.
BIX – The agent runs on a BIX node for BIX jobs.
Custom1, Custom2, Custom3, Custom4, Custom5 – The agent runs on the selected custom node.
- Remove the new association by editing the Agent schedule rule (optional).