You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit bbe6b26
Browse filesBrowse the repository at this point in the historyBrowse files
Copy file name to clipboardExpand all lines: docs/quantum-scheduling.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -63,7 +63,7 @@ The quantum handler also enforces admission control, which is always on unless t
63
63
5. When the task is next in line, or already running, annotate each worker with the job id and the session, then remove the gate.
64
64
6. Wait for the workers to reach Succeeded or Failed, write the done marker so the scout's release proceeds, and exit.
65
65
66
-
If the task is never found or fails, the sidecar ungates anyway so the workers are not stranded, and exits non zero so it shows.
66
+
The sidecar ungates the workers only when the scout's task is running or has completed. If the task fails, is cancelled, or is never found, the workers stay gated, the sidecar tells the scout to release its session at once, and it exits non zero so it shows. Delete the job to clear the gated workers. The one exception is a rehearsal, where the scout exits without submitting anything, for example with no credentials. Then the workers are released with no session.
0 commit comments