Repository navigation
Conversation
|
|
Problem: Instance-local properties such as queue membership may change while an instance is running, but the component making the change has no way to confirm that the scheduler has applied it. A job whose constraint names a property the scheduler has not yet applied may be rejected as unsatisfiable. Define a sched.property-update request from the resource module to the scheduler, carrying the properties to add and remove. The response is the confirmation: the resource module sends the request before applying the change to its own copy of R, and fails the operation if the scheduler returns an error. An ENOSYS response fails the operation, unlike sched.expiration in RFC 27 where it is treated as success. An outdated expiration affects the quality of a schedule, while an unapplied property causes jobs that name it to be rejected. Assisted-by: Claude:Opus-5
Problem: The acquire protocol defines property-add and property-remove keys for announcing a property change to the scheduler, but the protocol is one-way. The scheduler does not respond to acquire responses, so the component making the change cannot confirm the scheduler applied it before a job names that property. A job that names an unapplied property may be rejected as unsatisfiable. Remove both keys. sched.property-update serves the same purpose and is acknowledged, so there is no case where the acquire responses are the right mechanism. Nothing implements them. Assisted-by: Claude:Opus-5
grondo
force-pushed
the
rfc28-property-update
branch
from
October 15, 2026 00:42
02e0c03 to
21f6447
Compare
|
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem: The
property-addandproperty-removeacquire responses announce a change to one or more resource properties property, but the acquire protocol is one-way, so the sender cannot confirm the scheduler applied it. This could result in a runtime queue being started before the scheduler knows about its property.Replace them with a
sched.property-updaterequest carrying the same payload. The response becomes the confirmation. Nothing implements the acquire responses today, so they are unused and unnecessary. Remove them.