Limits provide simple load management by limiting the number of tasks
submitted by a specific ecflow_server
We have learnt from experience that suite designers were using trigger‘s in
two different ways: as data dependency triggers and as courtesy triggers.
Triggers where designed for the former. The latter are used to prevent too
many jobs running at once and are actually an artificial way of queuing jobs.
Because ecFlow does not distinguish between the two sorts of triggers, suites can become
difficult to maintain after a while. So the concept of limit was introduced.
Limits are declared with the limit keyword
 

 

 

What to do

  1. Edit the changes
  2. Replace the suite definition
  3. In ecflow_ui , observe the triggers of the limit l1
  4. Open the Info panel for l1
  5. Change the value of the limit
  6. Open the Why? panel for one of the queued tasks of /test/f5