...
There are two possible parts to a solution Process Classes and Locks Examples for the use of locks.
Process classes
Process classes are objects which can be assigned to jobs. In the situation described here we are interested in using the process class to restrict the number of instances of a job that can be run at any one time. Setting the "tasks" parameter to "0" for a job will allow all instances of that job to end regularly but prohibit new instances from starting.
We recommend setting up "Resource Maintenance" jobs to automatically set the tasks parameter to 0 for all the jobs using a resource and then reset the value after maintenance.
See also:
- The "How to use Process Classes" FAQ, which provides a good introduction to process classes.
- The Process Classes section in the JobScheduler Reference Manual, which covers the subject in more detail.
...
Note that in cluster operation all the JobSchedulers in a cluster will be using the same database, meaning that for database maintennace all jobs being executed by all the JobSchedulers will have to be stopped. In addition the JobSchedulers themselves will have to be suspended as the will otherwise continue to write their heartbeats into the database.
Locks
See also:
- The "LocksExamples for the use of locks" FAQ, which provides a good introduction to using locks.
- The Locks section in the JobScheduler Reference Manual, which covers the subject in more detail.