If you have a two-node cluster, and you don't want both services running on the same node, then if one node goes down your whole cluster is defunct. So ... what's the problem with using "run exclusively"? I realize this locks each service to a particular node, but if you don't want them running on the same node then there's no functional difference between that and what you want for a two-node cluster. -g Jure Pečar wrote: > On Fri, 10 Feb 2006 15:34:05 +0000 > Karl Podesta <kpodesta@xxxxxxxxxxxxxxx> wrote: > > >>What version of Cluster Suite are you running? > > > The one for RHEL4. > > >>There is an option (checkbox) somewhere in the GUI of Cluster Suite 4 >>to allow "run exclusively on this node", I think in the section for >>adding a service. Can't remember seeing it in the documentation, I >>remember it being hard to find. > > > Yes, I've seen it, but that's not what I want. > > >>Alternatively you could try creating a failover domain specifically >>for that service, so that it will only failover (once started) onto >>nodes you specify in that domain, although the above solution is the >>one you should probably use if you can find it. > > > That would be an option, but I have a two node cluster, so failover domains do not give me this. > > I'm thinkig of simply adding appropriate checks to init scripts of these two services, so if one is already up, the other would fail on start and the cluster is going to try starting it on the other node (hopefully). > > -- Linux-cluster@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/linux-cluster
