[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Condor-users] Flocking and high availability


Take a look at the "How to have execute machines belong to multiple pools" Admin Recipe (https://condor-wiki.cs.wisc.edu/index.cgi/wiki?p=HowToHaveExecuteMachines) that shows how to configure a super-pool over all your sub-pools and gives you the benefit of flocking  in a better way and "HA" for the matchmaking process.


Ian Cottam <Ian.Cottam@xxxxxxxxxxxxxxxx>
Sent by: condor-users-bounces@xxxxxxxxxxx

07/11/2011 09:49

Please respond to
Condor-Users Mail List <condor-users@xxxxxxxxxxx>

"condor-users@xxxxxxxxxxx" <condor-users@xxxxxxxxxxx>
[Condor-users] Flocking and high availability

Dear all,

To ease our problems with wake-on-lan, I am thinking of changing our
Condor topology from one big pool across campus to lots of little ones
connected by flocking.

We use teaching cluster PCs as our Condor Pool, and the idea is that one
of the PCs in each cluster would be the local match maker. Jobs would
(exclusively) flock from our central submitter/matchmaker pair to the
local pools. The teaching cluster PCs are not submit nodes so they don't
need any flock_to config lines.

Now, the obvious question arises: what if the PC in a local pool we have
chosen as local match maker is down? Looking at the High Availability part
of the manual it says you can have multiple negotiators, BUT it further
states that this does not work in the case of flocking.

My question is would it work in my case of restricted flocking (getting
jobs from one central submitter/matchmaker)?
I suspect not, but would appreciate a response from the gurus out there :-)

Many thanks

Ian Cottam
IT Services for Research
Faculty of Engineering and Physical Sciences
The University of Manchester
"The only strategy that is guaranteed to fail is not taking risks." Mark

Condor-users mailing list
To unsubscribe, send a message to condor-users-request@xxxxxxxxxxx with a
subject: Unsubscribe
You can also unsubscribe by visiting

The archives can be found at:

This message is intended solely for the use of its addressee and may contain privileged or confidential information. All information contained herein shall be treated as confidential and shall not be disclosed to any third party without Embraer’s prior written approval. If you are not the addressee you should not distribute, copy or file this message. In this case, please notify the sender and destroy its contents immediately.
Esta mensagem é para uso exclusivo de seu destinatário e pode conter informações privilegiadas e confidenciais. Todas as informações aqui contidas devem ser tratadas como confidenciais e não devem ser divulgadas a terceiros sem o prévio consentimento por escrito da Embraer. Se você não é o destinatário não deve distribuir, copiar ou arquivar a mensagem. Neste caso, por favor, notifique o remetente da mesma e destrua imediatamente a mensagem.