Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

rfc27: support partial release #421

Merged
merged 1 commit into from
Aug 8, 2024
Merged

rfc27: support partial release #421

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
25 changes: 18 additions & 7 deletions spec_27.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -44,8 +44,8 @@ behalf of jobs.
A scheduler implementation registers the generic service name ``sched``
and provides several well known service methods. The job manager requests
resources from the scheduler with a ``sched.alloc`` request when a job enters
SCHED state. It releases resources with a ``sched.free`` request when a job
enters CLEANUP state.
SCHED state. It releases resources with one or more ``sched.free`` requests
after a job enters CLEANUP state.

The simplest imaginable scheduler satisfies ``sched.alloc`` requests in order
until it is out of resources, then blocks until ``sched.free`` requests
Expand Down Expand Up @@ -569,16 +569,22 @@ The request MAY fail, for example if:
Free
====

The job manager SHALL send a ``sched.free`` request when a job that is
holding resources enters CLEANUP state. The request payload consists of
The job manager SHALL send one or more ``sched.free`` requests to release
allocated resources to the scheduler. The request payload consists of
a JSON object with the following REQUIRED keys:

id
(integer) job ID

R
(object) RFC 20 resource set from which the ``scheduling`` key MAY be
omitted.
omitted. This resource set MAY be a subset of the original allocation.

and the following OPTIONAL key:

final
(boolean) If present and true, this free request is the final one for the
job. If absent or false, more free requests are forthcoming for the job.

Example:

Expand All @@ -597,11 +603,16 @@ Example:
"expiration": 1710076122
}
}
"final":true
}


Upon receipt of the ``sched.free`` request, the scheduler SHOULD mark the
job's resources as available for reuse.
Upon receipt of a ``sched.free`` request, the scheduler SHOULD mark the
designated resources as available for reuse.

When a job's resources are released with multiple ``sched.free`` requests,
the scheduler MAY assume that the resources associated with a given rank
in the original allocation are never split over multiple free requests.

There is no response.

Expand Down
Loading