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.

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

rfc14: need a way to specify max duration in jobspec #333

Open
grondo opened this issue May 20, 2022 · 0 comments
Open

rfc14: need a way to specify max duration in jobspec #333

grondo opened this issue May 20, 2022 · 0 comments

Comments

@grondo
Copy link
Contributor

grondo commented May 20, 2022

The RFC 14 definition of the duration attribute is currently:

duration

The value of the duration attribute is a floating-point number greater than or equal to zero representing
time span in seconds. If duration is greater than zero, then the scheduler SHALL allocate the requested
resources for the number of seconds specified in duration. A duration value of 0. SHALL be interpreted as
unlimited or unset, and the scheduler SHALL use a duration that is the minimum of any configured duration
default and the time span to the currently defined instance expiration. If no default duration is configured,
and the current instance has no expiration, then resources shall be allocated without expiration.

As noted by @ryanday36 in #332, a way to specify that a job should get the maximum queue time limit instead of the default time limit would be a nice feature. One idea would be to use something like the maximum positive integer that can be represented as 32 bit floating-point (2^24? Or a little over 6 months). Another idea would be to relax the requirement that duration be positive and allow -1. to represent a request for the maximum allowable duration.

Either way, frontend tools could offer a special option or -t max and substitute whatever value we decide upon.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant