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

Investigate job maxMinutes semantics #35

Open
richcar58 opened this issue May 31, 2023 · 0 comments
Open

Investigate job maxMinutes semantics #35

richcar58 opened this issue May 31, 2023 · 0 comments
Assignees
Labels
enhancement New feature or request

Comments

@richcar58
Copy link

Investigate whether a job's maxMinutes should be calculated from the time the job is submitted to Tapis, from the Slurm submission time, or from the beginning of job execution. Part of the investigation is to determine whether queue time and runtime are both included in the job expiration check. This involves how monitoring policies are initialized.

It's possible we might want another time, say maxTapisMinutes, that distinguishes between the duration a job will be handled by Tapis and the runtime allowed on a system.

No matter what we chose, we need better logging and user messages when a job times out because it's been waiting in a slurm queue so long that as soon as it starts to run it's Tapis timeout is exceeded.

@richcar58 richcar58 added the enhancement New feature or request label May 31, 2023
@richcar58 richcar58 self-assigned this May 31, 2023
@scblack321 scblack321 self-assigned this Dec 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
Status: To Do
Development

No branches or pull requests

2 participants