1CONDOR_VACATE(1)                HTCondor Manual               CONDOR_VACATE(1)
2
3
4

NAME

6       condor_vacate - HTCondor Manual
7
8       Vacate jobs that are running on the specified hosts
9
10

SYNOPSIS

12       condor_vacate [-help | -version ]
13
14       condor_vacate [-graceful | -fast ] [-debug ] [-pool centralmanagerhost‐
15       name[:portnumber]] [ -name hostname | hostname | -addr "<a.b.c.d:port>"
16       | "<a.b.c.d:port>" | -constraint expression | -all ]
17

DESCRIPTION

19       condor_vacate  causes  HTCondor to checkpoint any running jobs on a set
20       of machines and force the jobs to vacate the machine.  The  job(s)  re‐
21       mains in the submitting machine's job queue.
22
23       Given  the (default) -graceful option, a job running under the standard
24       universe will first produce a checkpoint  and  then  the  job  will  be
25       killed.  HTCondor  will  then restart the job somewhere else, using the
26       checkpoint to continue from where it left off. A job running under  the
27       vanilla  universe is killed, and HTCondor restarts the job from the be‐
28       ginning somewhere else. condor_vacate has no effect on a  machine  with
29       no HTCondor job currently running.
30
31       There  is generally no need for the user or administrator to explicitly
32       run condor_vacate. HTCondor takes care of jobs in  this  way  automati‐
33       cally following the policies given in configuration files.
34

OPTIONS

36          -help  Display usage information
37
38          -version
39                 Display version information
40
41          -graceful
42                 Inform the job to checkpoint, then soft-kill it.
43
44          -fast  Hard-kill jobs instead of checkpointing them
45
46          -debug Causes  debugging  information to be sent to stderr, based on
47                 the value of the configuration variable TOOL_DEBUG.
48
49          -pool centralmanagerhostname[:portnumber]
50                 Specify a pool by giving the central manager's host name  and
51                 an optional port number
52
53          -name hostname
54                 Send the command to a machine identified by hostname
55
56          hostname
57                 Send the command to a machine identified by hostname
58
59          -addr "<a.b.c.d:port>"
60                 Send   the   command   to   a  machine's  master  located  at
61                 "<a.b.c.d:port>"
62
63          "<a.b.c.d:port>"
64                 Send the command to a machine located at "<a.b.c.d:port>"
65
66          -constraint expression
67                 Apply this command only to machines matching the given  Clas‐
68                 sAd expression
69
70          -all   Send the command to all machines in the pool
71

EXIT STATUS

73       condor_vacate  will  exit with a status value of 0 (zero) upon success,
74       and it will exit with the value 1 (one) upon failure.
75

EXAMPLES

77       To send a condor_vacate command to two named machines:
78
79          % condor_vacate  robin cardinal
80
81       To send the condor_vacate command to a machine within  a  pool  of  ma‐
82       chines other than the local pool, use the -pool option. The argument is
83       the name of the central manager for the pool. Note that one or more ma‐
84       chines  within  the  pool must be specified as the targets for the com‐
85       mand. This command sends the command to  a  the  single  machine  named
86       cae17  within  the pool of machines that has condor.cae.wisc.edu as its
87       central manager:
88
89          % condor_vacate -pool condor.cae.wisc.edu -name cae17
90

AUTHOR

92       HTCondor Team
93

95       1990-2021, Center for High Throughput Computing, Computer Sciences  De‐
96       partment,  University  of  Wisconsin-Madison, Madison, WI, US. Licensed
97       under the Apache License, Version 2.0.
98
99
100
101
1028.8                              Aug 23, 2021                 CONDOR_VACATE(1)
Impressum