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 hello responses #433

Merged
merged 2 commits into from
Nov 20, 2024
Merged

rfc27: support partial hello responses #433

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
95b6148
rfc27: add 'free' key to hello response
garlick Nov 15, 2024
b7b1284
rfc27: add optional partial-ok hello flag
garlick Nov 15, 2024
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
26 changes: 21 additions & 5 deletions spec_27.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -135,11 +135,19 @@ Hello
=====

Before any other RPCs are sent to the job manager, the scheduler SHALL
send an empty request to ``job-manager.sched-hello`` with the
FLUX_MSGFLAG_STREAMING flag set. The job manager SHALL send one
response message for each job with allocated resources. Each response
payload SHALL consist of a JSON object with the following REQUIRED
keys:
send a request to ``job-manager.sched-hello`` with the FLUX_MSGFLAG_STREAMING
flag set. The request payload SHALL either be empty or consist of a JSON
object with the following OPTIONAL keys:

partial-ok
(boolean) The scheduler SHALL set this flag to ``true`` if it can handle
the ``free`` key in hello responses. That is, it can process
jobs with partially released resource sets. If this key is missing it
SHALL be interpreted as ``false``.

The job manager SHALL send one response message for each job with
allocated resources. Each response payload SHALL consist of a JSON object
with the following REQUIRED keys:

id
(integer) job ID
Expand All @@ -153,6 +161,13 @@ userid
t_submit
(double) job submission time

and the following OPTIONAL key:

free
(string) An RFC 22 idset representing the ranks (execution targets)
of this job's resource set that have already been freed. If this key
is omitted, the scheduler SHALL assume the empty set.

Example:

.. code:: json
Expand All @@ -162,6 +177,7 @@ Example:
"priority": 43444,
"userid": 5588,
"t_submit": 1552593348.073045,
"free":"1-16,18",
}

For each job response, the scheduler SHALL mark its assigned resources
Expand Down
Loading