Mailing List Archives
Authenticated access
|
|
|
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [HTCondor-users] giving priority to a job already queued
- Date: Thu, 18 Jun 2020 18:35:44 -0500
- From: Todd Tannenbaum <tannenba@xxxxxxxxxxx>
- Subject: Re: [HTCondor-users] giving priority to a job already queued
On 6/18/2020 5:01 AM, htcondor-users@xxxxxxxxxxx wrote:
Hi All,
I have a job in the queue that I would really like to run as soon as possible.
Is there an easy way to tell condor to run this particular job next ? (I'm the administrator, not an impatient user.)
Regards,
Daniela
I assume that all the slots on your pool are already busy, else this queued job would soon start running....
So I thus assume what you want to do is run this job instead of some other job that is currently running.
Administrators have the power to do this! :) Specifically, users specified in the condor_config with QUEUE_SUPER_USERS
have the power... by default user root and user condor are QUEUE_SUPER_USERS.
The solution is to use the condor_now tool. On your submit host (where the schedd runs), su to root (or to any other
QUEUE_SUPER_USER), and then run condor_now with the job_id of the important job you want to run now, and the job_id you
want to vacate and give the resources to your important job. Do "man condor_now" for details, or see
https://htcondor.readthedocs.io/en/latest/man-pages/condor_now.html
Hope this helps,
Todd