This is correct. There is no default in the AP for all jobs, but you can use a JOB_TRANSFORM in the AP to set one of these attributes for jobs as they are submitted.
-tj
From: HTCondor-users <htcondor-users-bounces@xxxxxxxxxxx> on behalf of Belakovski, Nickolai via HTCondor-users <htcondor-users@xxxxxxxxxxx>
Sent: Monday, October 7, 2024 3:32 PM To: HTCondor-Users Mail List <htcondor-users@xxxxxxxxxxx> Cc: Belakovski, Nickolai <nickolai.belakovski@xxxxxxxx> Subject: Re: [HTCondor-users] Max Runtime Limit
I think you're looking for allowed_execute_duration or allowed_job_duration, see the reference here:
https://htcondor.readthedocs.io/en/latest/man-pages/condor_submit.html
I think the main difference between them is that if a job exceeds its allowed_execute_duration then it goes into hold and it can't be put back into a run state, whereas allowed_job_duration resets when the job leaves the running state. So I guess job_duration
would be better because if you have a job that it legitimately taking a long time and not just spinning, you could kick it and let it keep going. But I'm not sure as I'm only just learning these commands so I don't have practical experience with them yet.
Nickolai
From: HTCondor-users <htcondor-users-bounces@xxxxxxxxxxx> on behalf of Sandeep K. Joshi via HTCondor-users <htcondor-users@xxxxxxxxxxx>
Sent: Monday, October 7, 2024 10:47 AM To: htcondor-users@xxxxxxxxxxx <htcondor-users@xxxxxxxxxxx> Cc: Sandeep K. Joshi <skjoshi@xxxxxxxx> Subject: [HTCondor-users] Max Runtime Limit
Hello All,
Is there a htcondor config default value (system side, not specified by users in their jobscript) for the maximum time a job is allowed to run ? --
Regards, Sandeep |