[Documentation] Flux add `duration` to jobspec
A pull request for this has already been merged.
- #930 by @jan-janssen — merged
- Dominant language
- Python
- Stars
- 77
- Forks
- 7
- Avg merge
- 10h 32m
- Merged PRs (30d)
- 12
Description
Hi All,
Would it be possible to add duration to the jobspecV1 for flux execution? I was trying to come up with the clean way to enforce a timeout with multiple jobs, and it seems like having a duration set from the flux-side might be a clean way to track this:
Which seems to get referenced by the resource_dict here:
spawner_flux.py
This might clash a bit with the logic for executorlib if the idea with the flux executor is to start all these processes ("jobs") then submit multiple python processes to each one.
Either way, suggestions for how to handle timeouts / killing futures after a set duration after execution begins would be nice.
-Michael.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the Flux Jobspec documentation linked in the issue and the resource_dict usage in src/executorlib/task_scheduler/interactive/spawner_flux.py. Review the closed pull request #930 and clarify whether duration applies to Flux jobs or executor futures; done requires an agreed timeout behavior and corresponding implementation coverage.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- hpc, python
- Domain
- backend, distributed-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100