You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
The text was updated successfully, but these errors were encountered: