Starting Situation
- The JobScheduler Master might not respond in time to the JOC GUI when there is high system load (CPU, memory) on the server that the Master is operated for.
- In such a situation the JobScheduler Master will primarily serve jobs and delay responses to the JOC GUI.
- As a result the JOC GUI becomes unresponsive as it includes timeout settings for responses from a JobScheduler Master.
Use Cases
Many operations of the JOC GUI are available from the CLI. Such operations can be carried out more effectively by the CLI, i.e. they cause less overhead in a situation when resources are limited.
Suspending and Resuming the JobScheduler Master
The Master can be paused with the following command:
Suspend-Master
Explanations
- A paused Master will not start new tasks.
- Any running tasks are continued
The Master can be continued with the following command:
Resume-Master
Explanations
- A continued Master will immediately start any enqueued tasks.
- Task starts that have been scheduled for a point in time when the Master was paused will be carried out immediately.
Increasing the timeout for JobScheduler Master responses
The JobScheduler CLI uses a default of 15s for expected responses of a Master. In situatons with a high load this value could be increased:
Set-Option -WebRequestTimeout 60000
Explanations
- The
Set-Optioncmdlet is used to increase the timeout to 60 seconds. - Values are specified in milliseconds.
Killing running tasks
See PowerShell CLI - Use Cases - Kill a number of tasks
Removing temporary ad hoc orders
See PowerShell CLI - Use Cases - Manage temporary orders