How To Shut Down Condor

How to shut down HTCondor without killing jobs

Known to work with HTCondor version: 7.0

How to shut down a single execute node without killing jobs

Issue the following command from the central manager, or, depending on your security policy, from wherever and as whomever you need to be to issue administrative commands.

condor_off -startd -peaceful <hostname>

How to shut down the whole pool without killing any jobs

Initiate a peaceful shutdown of all execute nodes. Issue the following command from the central manager, or, depending on your security policy, from wherever and as whomever you need to be to issue administrative commands.

condor_off -all -startd -peaceful

Once condor_status reports that the pool is empty of startds, shut everything else off:

condor_off -all -master

How to shut down a submit node after finishing all existing jobs in the queue

Disable new submissions to the schedd by adding the following to the configuration file:

MAX_JOBS_SUBMITTED=0

Once all jobs have completed, turn off HTCondor by issuing the following command from the central manager, or, depending on your security policy, from wherever and as whomever you need to be to issue administrative commands.

condor_off -schedd -peaceful <hostname>

How to shut down a submit node after finishing all running jobs in the queue

As of HTCondor 7.1.1, you can do this by issuing the following command from the central manager, or, depending on your seucrity policy, from wherever and as whomever you need to be to issue administrative commands.

condor_off -schedd -peaceful <hostname>

In versions prior to HTCondor 7.1.1, you can put all idle jobs on hold and then wait for the running jobs to finish. Run the following command as a user with administrative privileges in the queue (e.g. root).

condor_hold -constraint 'JobStatus == 1'

In this case, you may also wish to disable the submission of new jobs by adding the following to your configuration:

MAX_JOBS_SUBMITTED=0

How to shut down a submit node temporarily (e.g. to reboot the machine) without waiting for jobs to finish but doing as little damage as possible

Just shut down the schedd normally (graceful shutdown). Issue the following command from the central manager, or, depending on your seucrity policy, from wherever and as whomever you need to be to issue administrative commands.

condor_off -schedd <hostname>

During graceful shutdown of the schedd, all running standard universe jobs are stopped and checkpointed. All other jobs are left running (if they have a non-zero JobLeaseDuration , which is 20 minutes by default). The schedd gracefully disconnects from them in the hope of being able to later reconnect to the running jobs when it starts back up. If the lease runs out before the schedd reconnects to the jobs, then they are killed. Therefore, if you need a longer down time, you should increase the lease. You can increase the default by adding the following to your HTCondor configuration:

JobLeaseDuration = 5400
SUBMIT_EXPRS = $(SUBMIT_EXPRS) JobLeaseDuration