SIGTERM won't be set to any job whose
runtime is less than MaxJobRetirementTime with a "graceful"
shutdown/drain.
Hi all,
currently DEFRAG_SCHEDULE can be any one out of graceful, quick
and fast.
However, in a pool with many jobs not doing checkpoints at all or
ignoring SIGTERM altogether, I think it may be beneficial to
really wait for the jobs to finish if it only affects very, very
few nodes and one could accept the badput - just raising
MaxJobRetirementTime/MachineMaxVacateTime would probably not do
much as most jobs will still not intercept SIGTERM and still be
killed via a graceful shutdown.
Would there be other consequences I currently do not see, is there
already something in Condor I am overlooking or would this just be
a small change in Condor to have this as a new feature?
Cheers
Carsten
_______________________________________________
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/
![[Computer Systems Lab]](http://www.cs.wisc.edu/pics/csl_logo.gif){kind=logo}