Triggered Task node not available
Hello , Our snaplogic nodes are not load balanced currently. Snaplogic tied all of our production triggered task to one node. even though we have more than one node in production. If that nodes goes...
Forum Discussion
The scheduling is dynamic upon each scheduled trigger. This is done upon every trigger separately. The triggered tasks are tied to a particular plex, but not a particular node within the plex.
The scheduling will only choose nodes that are have the reasonable resources (threads, cpu, memory) to execute the pipeline associated with the triggered task, and ensures the JCC is responsive.
It is definitely possible to have a single node get multiple tasks scheduled on it continuously if it is the better fit to run the pipeline at that time.
However, you should be able to reasonably see why the scheduler chose the node it did, but once again it is dynamic and these values can change after scheduling the job so that is not always the case.
Yes, if your groundplex node is down, then using the cloud will try and find a node on the plex this task is configured for to host the triggered execution if there is one available. If all nodes are down then the job will not be run.
Hope this answers your questions. Let me know if I can clear anything else up.
