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

NAME

6       condor_vacate_job - HTCondor Manual
7
8       vacate jobs in the HTCondor queue from the hosts where they are running
9
10

SYNOPSIS

12       condor_vacate_job [-help | -version ]
13
14       condor_vacate_job  [  -pool centralmanagerhostname[:portnumber] | -name
15       scheddname ] | [-addr "<a.b.c.d:port>"] [-fast  ]  cluster...  |  clus‐
16       ter.process... | user... | -constraint expression ...
17
18       condor_vacate_job  [  -pool centralmanagerhostname[:portnumber] | -name
19       scheddname ] | [-addr "<a.b.c.d:port>"] [-fast ] -all
20

DESCRIPTION

22       condor_vacate_job finds one or more jobs from the  HTCondor  job  queue
23       and vacates them from the host(s) where they are currently running. The
24       jobs remain in the job queue and return to the idle state.
25
26       A running job running will be sent a soft kill signal (SIGTERM  by  de‐
27       fault,  or  whatever is defined as the SoftKillSig in the job ClassAd),
28       and HTCondor will restart the job from the beginning somewhere else.
29
30       If the -fast option is used, the job(s) will be immediately killed.
31
32       If the -name option is specified, the named condor_schedd  is  targeted
33       for  processing.  If the -addr option is used, the condor_schedd at the
34       given address is targeted for processing.  Otherwise,  the  local  con‐
35       dor_schedd is targeted. The jobs to be vacated are identified by one or
36       more job identifiers, as described below. For any given job,  only  the
37       owner  of  the  job  or  one  of  the queue super users (defined by the
38       QUEUE_SUPER_USERS macro) can vacate the job.
39
40       Using condor_vacate_job on jobs which are not currently running has  no
41       effect.
42

OPTIONS

44          -help  Display usage information
45
46          -version
47                 Display version information
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 scheddname
54                 Send the command to a machine identified by scheddname
55
56          -addr "<a.b.c.d:port>"
57                 Send the command to a machine located at "<a.b.c.d:port>"
58
59          cluster
60                 Vacate all jobs in the specified cluster
61
62          cluster.process
63                 Vacate the specific job in the cluster
64
65          user   Vacate jobs belonging to specified user
66
67          -constraint expression
68                 Vacate all jobs which match the job ClassAd  expression  con‐
69                 straint
70
71          -all   Vacate all the jobs in the queue
72
73          -fast  Perform a fast vacate and hard kill the jobs
74

GENERAL REMARKS

76       Do  not confuse condor_vacate_job with condor_vacate.  condor_vacate is
77       given a list of hosts to vacate, regardless of what jobs happen  to  be
78       running on them. Only machine owners and administrators have permission
79       to use condor_vacate to evict jobs from a given host. condor_vacate_job
80       is given a list of job to vacate, regardless of which hosts they happen
81       to be running on. Only the owner of the jobs or queue super users  have
82       permission to use condor_vacate_job.
83

EXAMPLES

85       To vacate job 23.0:
86
87          $ condor_vacate_job 23.0
88
89       To vacate all jobs of a user named Mary:
90
91          $ condor_vacate_job mary
92
93       To vacate all vanilla universe jobs owned by Mary:
94
95          $ condor_vacate_job -constraint 'JobUniverse == 5 && Owner == "mary"'
96
97       Note that the entire constraint, including the quotation marks, must be
98       enclosed in single quote marks for most shells.
99

EXIT STATUS

101       condor_vacate_job will exit with a status value of 0 (zero)  upon  suc‐
102       cess, and it will exit with the value 1 (one) upon failure.
103

AUTHOR

105       HTCondor Team
106
108       1990-2023,  Center for High Throughput Computing, Computer Sciences De‐
109       partment, University of Wisconsin-Madison, Madison,  WI,  US.  Licensed
110       under the Apache License, Version 2.0.
111
112
113
114
115                                 Oct 02, 2023             CONDOR_VACATE_JOB(1)
Impressum