Re: [HTCondor-users] Can periodic_release query completed jobs?

[Matthew T West <m.t.west@xxxxxxxxxxxx>]

When in doubt, DAGMan.

You don't have to reinvent and debug things that already have first party support. I know its an extra few steps, but it's a far better use of your time than trying to rig something up for this one situ.

~ Matt

Matthew T. West
DevOps & HPC SysAdmin
University of Exeter, Research IT
57 Laver Building, North Park Road, Exeter, EX4 4QE, United Kingdom

On 25/09/2024 18:41, Belakovski, Nickolai via HTCondor-users wrote:

CAUTION: This email originated from outside of the organisation. Do not click links or open attachments unless you recognise the sender and know the content is safe.

Hello,

I'm trying to submit one job and have it depend on another job. I know I can use DAGMan for this, but just for the moment I was hoping I could do it with hold and periodic_release. I submitted a long running job and then tried to submit another one with the following lines in the submit file:

hold = True

periodic_release = (ClusterId == 11) && (JobId == 0) && (JobStatus == 4)

Where 11.0 was the id of the long running job. I wasn't sure if this would work since it's not clear which context JobStatus was evaluated in, and sure enough it didn't, the job stated in the hold state.

Is there any way to achieve what I'd trying to do with periodic_release, or should I just go for DAGMan?

Thanks so much,

Nickolai

_______________________________________________
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/