Ensure the optimal use of system resources by limiting the number of concurrent
active data flow runs that are allowed for a node type, such as Batch or Search. If the
limit is reached, the system queues subsequent runs and waits for active runs to stop or
finish before queued runs can start.
By limiting the number of active runs, you can ensure that you do not run out of system
resources, for example, due to large numbers of batch data flow runs.
For more information about the max_active_runs dynamic system
settings that define these limits, see Data flow run limits.
- In the navigation pane of Dev Studio,
- Expand the SysAdmin category, and then
click Dynamic System Settings.
- In the Setting purpose column, click the
- In the Search Text field, enter
max_active_runs, and then click
- Perform one of the following actions:
- If the dynamic system setting that you want to change is available in
the table, click the row for that setting and go to step 7.
- If you want to add a dynamic system setting that is not in the table, go
to step 6.
- Add the dataflow/<node_type>/max_active_runs dynamic
system setting for a node type:
- On the Dynamic System Settings tab, click
- On the New tab, enter a short description of the
setting.For example: Limits active runs for PegaMKTSMS node
- In the Owning Ruleset field, enter
- In the Setting Purpose field, enter
where node_type is the case-sensitive name of the
node type that is associated with the data flow service.For example: dataflow/PegaMKTSMS/max_active_runs
- Click Create and open.
- On the Settings tab, in the Value
field, enter the limit for active runs that are allowed for the node type.
Define the limit as a number greater than zero, for example, 10. You can use
the special value –1 to indicate that the system can schedule an unlimited
number of runs for the node type.
- Click Save.
Note: After you change the dynamic system setting, it may take up to 5 minutes
for the new limit to take effect.