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

Periodically check whether jobs have been removed externally #643

Open
lauridsj opened this issue Jul 19, 2024 · 0 comments
Open

Periodically check whether jobs have been removed externally #643

lauridsj opened this issue Jul 19, 2024 · 0 comments
Labels

Comments

@lauridsj
Copy link

Hi,

I am using the HTCondorCluster on a regrettably rather unstable computing cluster, and face the issue that when jobs are removed / killed / crash before the worker even gets to connect to the scheduler (e.g. because on the worker side it doesnt even manage to source the python environment), it gets ignored and the jobs never get resubmitted. As far as I can tell, this is not a surprise since there currently seems to be no way of checking whether a job is running, in idle, or removed (i.e. by calling condor_q with HTCondor) if the worker has not yet connected. In principle, this issue should happen with other HPC systems as well, though I havent checked.
This could probably be done by periodically calling condor_q -nobatch, parsing the output, and comparing against the job ids of the workers that are supposed to be submitted. I am not sure whether there is already any part of the code that gets called periodically in this manner and could be used for this purpose; if there is and you could point me to it, I would be happy to try my hand at it.

Cheers and thank you,
Laurids

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants