Jobs might remain in a starting or running state when using SAS Grid Manager (SAS Workload Orchestrator).

These jobs overload the grid nodes because they never run to completion. As a result, the grid environment becomes unstable.

Note: SAS Grid Manager consumes 100% CPU when jobs remain in a starting or running state. You might notice or might not notice this CPU spike.

The hot fix for this issue addresses these issues.