Re: [HTCondor-users] update of condor-version and job-behaviour

[Greg Thain <gthain@xxxxxxxxxxx>]

Hi Martin:

When HTCondor is upgraded *on the worker node*, or, more generally, when 
the HTCondor worker node daemons restart for any reason:

Any running jobs are killed, will go back to the "I"dle state in the 
queue, and HTCondor will restart them, perhaps on another machine.

If you are more concerned about the badput from restarting a running 
job, than the potential loss of throughput from keeping cores idle, you 
can run "condor_off -peaceful" on the worker node before your upgrade, 
and condor will wait until all the jobs exit before it, itself exits, at 
which time you could upgrade the machine.

And just for completeness, upgrading the central manager will not evict 
jobs. Upgrading the access point (where the schedd runs) will not evict 
jobs, if the new daemons restart quickly enough.

-greg

> Hi !
>
> Which is the default behaviour of running jobs on an working-node on 
> which the condor-packages will be updated ...?
>
> a) the running jobs are running well with the old version, and each 
> job after update of the packages, they will start with the new 
> installed condor-version ?
>
> b) the running jobs will be canceld after the update and would be 
> re-scheduled with the new version?
>
> c) the running jobs will be cancled and will be lost
>
> d) ....
>
> cheers & thanks,
>
> ÂÂÂÂÂÂ Martin
>
> _______________________________________________
> 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/