CONDOR_VACATE(1) | HTCondor Manual | CONDOR_VACATE(1) |
condor_vacate - HTCondor Manual
Vacate jobs that are running on the specified hosts
condor_vacate [-help | -version ]
condor_vacate [-graceful | -fast ] [-debug ] [-pool centralmanagerhostname[:portnumber]] [ -name hostname | hostname | -addr "<a.b.c.d:port>" | "<a.b.c.d:port>" | -constraint expression | -all ]
condor_vacate causes HTCondor force jobs to vacate from a given set of machines. The job(s) remains in the submitting machine's job queue.
Given the (default) -graceful option, jobs are killed and HTCondor restarts the job from the beginning somewhere else. condor_vacate has no effect on a machine with no HTCondor job currently running.
There is generally no need for the user or administrator to explicitly run condor_vacate. HTCondor takes care of jobs in this way automatically following the policies given in configuration files.
condor_vacate will exit with a status value of 0 (zero) upon success, and it will exit with the value 1 (one) upon failure.
To send a condor_vacate command to two named machines:
$ condor_vacate robin cardinal
To send the condor_vacate command to a machine within a pool of machines other than the local pool, use the -pool option. The argument is the name of the central manager for the pool. Note that one or more machines within the pool must be specified as the targets for the command. This command sends the command to a the single machine named cae17 within the pool of machines that has condor.cae.wisc.edu as its central manager:
$ condor_vacate -pool condor.cae.wisc.edu -name cae17
HTCondor Team
1990-2024, Center for High Throughput Computing, Computer Sciences Department, University of Wisconsin-Madison, Madison, WI, US. Licensed under the Apache License, Version 2.0.
August 25, 2024 |