Understanding concurrent job execution
When a job includes multiple span actions, actions are executed in sequence (for example, action 1 runs followed by action 2 followed by action 3). When an action runs, BMC Network Automation implements the action concurrently across the targeted devices. Concurrency is supported for the Snapshot, Deploy to Stored, Deploy to Active, Commit, Reboot, Custom Actions, Scan Syntax and Deploy/Snapshot OS Image span actions. The default number of concurrent span actions is 20. See your system administrator to change this default, as necessary. For example:
- The user schedules a Snapshot job for a group with 100 devices. BMC Network Automation starts 20 concurrent Snapshot actions for devices in the group. When one Snapshot action completes, the next Snapshot action is immediately started.
- The user schedules two jobs to run concurrently. One is a Snapshot job for a group with 200 devices. The other is a Deploy to Active request to update SNMP community string for 40 devices. BMC Network Automation ensures the smaller Deploy to Active job is not starved by the larger Snapshot job. BMC Network Automation gives both jobs equal access to execute. If another job is queued, it joins the round robin request chain.