Conflicts: Difference between revisions
No edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
Obsidian supports completely customizable conflict configuration combined with custom prioritization. | |||
To accommodate your business' needs, any number of jobs can be configured to not run concurrently, even if scheduled to run at the same time. When jobs are set as conflicting and are scheduled to run at the same time, the chosen prioritization will determine the order of execution of the scheduled jobs. Any termination state, either success or failure, will release the next lower priority job to complete. These conflicts work even across multiple hosts. | To accommodate your business' needs, any number of jobs can be configured to not run concurrently, even if scheduled to run at the same time. When jobs are set as conflicting and are scheduled to run at the same time, the chosen prioritization will determine the order of execution of the scheduled jobs. Any termination state, either success or failure, will release the next lower priority job to complete. These conflicts work even across multiple hosts. | ||
If you have configured conflicting jobs, you will want to pay attention to the pickup buffer minutes configuration setting - see [[Job Features]]. This will determine the maximum number of minutes past the original scheduled time that the scheduled job will still be picked once higher priority conflicts have cleared. If this time limit passes, the scheduled job will be marked as Conflict Missed and will not be run. | If you have configured conflicting jobs, you will want to pay attention to the pickup buffer minutes configuration setting - see [[Job Features]]. This will determine the maximum number of minutes past the original scheduled time that the scheduled job will still be picked once higher priority conflicts have cleared. If this time limit passes, the scheduled job will be marked as Conflict Missed and will not be run. | ||
Revision as of 20:19, 21 February 2011
Obsidian supports completely customizable conflict configuration combined with custom prioritization.
To accommodate your business' needs, any number of jobs can be configured to not run concurrently, even if scheduled to run at the same time. When jobs are set as conflicting and are scheduled to run at the same time, the chosen prioritization will determine the order of execution of the scheduled jobs. Any termination state, either success or failure, will release the next lower priority job to complete. These conflicts work even across multiple hosts.
If you have configured conflicting jobs, you will want to pay attention to the pickup buffer minutes configuration setting - see Job Features. This will determine the maximum number of minutes past the original scheduled time that the scheduled job will still be picked once higher priority conflicts have cleared. If this time limit passes, the scheduled job will be marked as Conflict Missed and will not be run.
