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

How do we support SLURM time limit? #191

Open
jennydaman opened this issue Jan 24, 2022 · 1 comment
Open

How do we support SLURM time limit? #191

jennydaman opened this issue Jan 24, 2022 · 1 comment
Labels
Milestone

Comments

@jennydaman
Copy link
Collaborator

Time limit is a very influential aspect of a queued job's priority to a SLURM scheduler, so pman should be able to send time limits to Cromwell.

Simplest solution: let CROMWELL_TIMELIMIT be an environment variable for pman, and send it off in the WDL everytime. Multiple pman instances and multiple pfcon instances can be created to define multiple compute environments with different time limits.

Propose spec solution: add to the ChRIS plugin spec, plugin developers must provide an estimate of time needed, and timelimit should be part of resources_dict

@jennydaman jennydaman added this to the cromwell milestone Jan 24, 2022
@jennydaman jennydaman mentioned this issue Jan 24, 2022
@jennydaman
Copy link
Collaborator Author

For now, when configured with the Cromwell backend, pman supports an environment variable configuration TIMELIMIT_MINUTES. See wiki for details.

Multiple instances of pfcon+pman duo pairs can be deloyed where the TIMELIMIT_MINUTES setting is different for each one. These pairs should be registered to CUBE with corresponding names. That way, users can choose time limits as one of few hard-coded values.

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

No branches or pull requests

1 participant