[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [HTCondor-users] preserve on/off state over restart
- Date: Mon, 17 Mar 2014 10:02:08 -0500
- From: Brian Bockelman <bbockelm@xxxxxxxxxxx>
- Subject: Re: [HTCondor-users] preserve on/off state over restart
I'm drawing a blank.
What about integrating this into Puppet? I.e., after issuing the condor_off, also change the worker's puppet config to keep the service off.
On Mar 17, 2014, at 7:46 AM, Pek Daniel <pekdaniel@xxxxxxxxx> wrote:
> So far I've used condor_on/off to add/remove worker nodes (startds)
> to/from the cluster. The problem with that is startd or masterd
> apparently doesn't preserve this state over a reboot of the whole
> machine or a restart of the service. In a big cluster with thousands
> of worker nodes, nodes come and go all the time, so it'd be nice to
> have a way to turn off/on components persistently.
> I know there's no real bulletproof solution for this, but I'd be happy
> with at least an eventually consistent solution too :) Any idea?
> HTCondor-users mailing list
> To unsubscribe, send a message to htcondor-users-request@xxxxxxxxxxx with a
> subject: Unsubscribe
> You can also unsubscribe by visiting
> The archives can be found at: