Saving data instance at a node restarts agent on all nodes
Saving an Agent data instance at a node restarts the agent on all the nodes. This occurs post new platform change where the nodes classification is used. The agent data instances per node could be controlled. However, it must not change until it's deleted. Instances are not node specific with the change in node classification. When user shutdowns a agent on one node, the setting is overridden by the system during the next run. Errors occur in logs when agents overlap.
Unique constraint exception messages
Steps to Reproduce
- Use a multinode system
- Disable an agent on one node
- Shut down an agent on another node
- Save the instance of agent ruleset. Verify the behavior on both the nodes
The new run which is scheduled starts immediately when a previous run is in progress. Hence, the two runs of the same agent overlap.
Skip runs of an agent after saving if the previous run is still in progress.
Published May 2, 2019 - Updated October 8, 2020
0% found this useful
Have a question? Get answers now.
Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.