Allowing a Job to Specify Thread PoolLast Updated: 07/23/2018 Introduced in Version: 2.0
By default, the job scheduler runs all jobs in the same queue. This means that only one job will run at a time. For example, if Job A is scheduled to run at 5:00 PM and Job B is scheduled to run at 5:10 PM, but Job A takes 20 minutes to complete, Job B will not actually begin running until 5:20 AM because it could not start until Job A had completed. The job scheduler works like this to protect the server from being inundated by too many jobs running at once. However, in some cases a user may want to override this default behavior and allow a job to run in a separate job queue, thus allowing it to run in parallel with other jobs.
For this example we create five New Ad Sync Jobs. Name first Job A, then, set up a Calendar for the Job and click Finish.
In the similar manner we add 4 more New Ad Sync Jobs.
Jobs A ad B are going to be in the Default Queue Pool. We select Job C and select Edit [Advanced] option from the pop-up menu.
In the resulting window we locate Advanced > Values section and in Override Job Queue Name text-box type My Queue Y. Click Ok to save and close this window.
Then, we Edit Job D…
In the Job Edit window we define My Queue Y value for the Override Job Queue Name setting. Click Ok.
Finally, we Edit Job E.
For the Job E we define My Queue Z value for the Override Job Queue Name configuration. Click Ok to save.
Need more help with: Allowing a Job to Specify Thread Pool?
Contact us at email@example.com