These config knobs are meant to throttle the rate at which the Schedd will spend time removing jobs from the queue, not to provide a way to delay removal.
So the delay value is measured from the time the first job is ready to be removed, there is not a separate timer for each job.
Also using these throttling knobs will affect condor_rm as well as job completion, which is probably not what you want.
The way to have jobs remain in the queue after they are completed is to use the OnExitRemove _expression_ of the job. And to have them removed at some time in the future you can use SYSTEM_PERIODIC_REMOVE, or the PeriodicRemove _expression_ of the job.
-tj
From: HTCondor-users <htcondor-users-bounces@xxxxxxxxxxx> on behalf of Mary Hester <maryh@xxxxxxxxx>
Sent: Friday, October 11, 2024 4:28 AM To: HTCondor-Users Mail List <htcondor-users@xxxxxxxxxxx> Subject: [HTCondor-users] JOB_IS_FINISHED_* config options not removing jobs with delay Hi all,
I tried to implement a short delay (10 min) before jobs are removed from the condor_q output, but this went horribly wrong and seemed to keep the jobs around for days. In our schedd configuration I added: # manual says delay time is in seconds: https://urldefense.com/v3/__https://htcondor.readthedocs.io/en/latest/admin-manual/configuration-macros.html*JOB_IS_FINISHED_INTERVAL__;Iw!!Mak6IKo!Kiet-p_zHlVE2SLz6EiCjj__3XH9ASU7jHOK5o1liNmMVZ6gohTk6MhJgubfuXaMuq8fST_v5q_9OHY4NA$ JOB_IS_FINISHED_INTERVAL=600 JOB_IS_FINISHED_COUNT=1000 I believe that second number is ok to be a high value since we do not want to limit the number of jobs that are allowed to leave the condor_schedd. Was there something I was missing here? Thanks, Mary _______________________________________________ HTCondor-users mailing list To unsubscribe, send a message to htcondor-users-request@xxxxxxxxxxx with a subject: Unsubscribe You can also unsubscribe by visiting https://lists.cs.wisc.edu/mailman/listinfo/htcondor-users The archives can be found at: https://lists.cs.wisc.edu/archive/htcondor-users/ |