Re: [HTCondor-users] condor_status update time

[Steven C Timm <timm@xxxxxxxx>]

Isn't there also a knob by which you can also control how long classads live in the collector,

i.e. if they are not updated in <n> seconds they just drop out?

Steve Timm

---

From: HTCondor-users <htcondor-users-bounces@xxxxxxxxxxx> on behalf of Todd Tannenbaum <tannenba@xxxxxxxxxxx>
Sent: Tuesday, October 10, 2017 10:22:46 AM
To: HTCondor-Users Mail List
Subject: Re: [HTCondor-users] condor_status update time

 

On 10/10/2017 9:58 AM, John M Knoeller wrote:
> To shut the daemons down cleanly, you can use condor_off -master.  Or
> you can send the condor_master a SIGTERM signal, which has the same
> effect.  Then you have to give the condor_startd and condor_master time
> to shutdown cleanly.  I believe that this can take as much as 2 minutes
> if the condor_startd is running a job and the job doesn’t respond to
> SIGTERM, (or doesn’t respond quickly).
>

Quick comment on the above:

If you do not want to be patient with running jobs, you could add the
"-fast" flag like so:
   condor_off -fast -master  [node name]
which typically shuts things down within a few seconds, killing the job
with SIGKILL if needed.  This should be what happens when you do a
'systemctl stop condor'.

regards,
Todd
_______________________________________________
HTCondor-users mailing list
To unsubscribe, send a message to htcondor-users-request@xxxxxxxxxxx with a
subject: Unsubscribe
You can also unsubscribe by visiting
https://lists.cs.wisc.edu/mailman/listinfo/htcondor-users

The archives can be found at:
https://lists.cs.wisc.edu/archive/htcondor-users/