[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Condor-users] Mixed 6.8.6 and 6.9.5 installation
- Date: Tue, 04 Dec 2007 10:41:46 -0600
- From: Dan Bradley <dan@xxxxxxxxxxxx>
- Subject: Re: [Condor-users] Mixed 6.8.6 and 6.9.5 installation
Yes, you should be able to run 6.9.5 on your submit node and/or central
manager while running 6.8.6 on some/all execute nodes.
If you want to upgrade without killing any running jobs, it is possible,
at least for vanilla universe configured with a long enough
JobLeaseDuration to let you get the upgrade done. However, if that is
not hugely important, it is simpler to just shut down your submit node
normally (which will stop all jobs in 6.8.6), do the upgrade, and then
start it back up. I'd recommend upgrading the central manager first and
then doing the submit node once the new central manager daemons are up
Robert E. Parrott wrote:
We have a cluster of 240 processors, managed by condor v6.8.6, and
have some users who would like to schedule 1000 jobs at once. At full
throttle I can imagine seeing 5000 jobs in under condor_q if we let
the users run free.
I understand that schedd and other daemons are single threaded, and
with that many jobs can show significantly reduced performance, but
that in v6.9.5 this has been refactored, which is a significant
attraction to the development series.
My question is how one might make use of the updated condor daemons
on the frontend and submit machine, without having to upgrade all the
compute nodes. Would this be possible? What would be needed to do so
in a graceful manner?
Condor-users mailing list
To unsubscribe, send a message to condor-users-request@xxxxxxxxxxx with a
You can also unsubscribe by visiting
The archives can be found at: