dvossel at redhat
Feb 25, 2012, 4:08 PM
Post #3 of 4
----- Original Message -----
Re: Question about master/slave resource promotion
[In reply to]
> From: "Florian Haas" <florian [at] hastexo>
> To: "The Pacemaker cluster resource manager" <pacemaker [at] oss>
> Sent: Saturday, February 25, 2012 2:52:54 AM
> Subject: Re: [Pacemaker] Question about master/slave resource promotion
> On Sat, Feb 25, 2012 at 12:31 AM, David Vossel <dvossel [at] redhat>
> > Hey,
> > I have a 2 node cluster with a multi-state master/slave resource.
> > When the multi-state resources start up on each node they enter
> > the Slave role. At that point I can't figure out how to promote
> > the resource to activate the Master role on one of the nodes. Is
> > there anything special I need to do to get an instance of my
> > multi-state resource to promote to the Master role?
> Yeah, actually using a resource type that is capable of running in
> master/slave mode would be a good start. :) Use
> instead of ocf:pacemaker:Dummy in your test setup.
The example works with the Stateful resource agent, and your comment helped me understand how this concept works better. I was not aware resource agents knew anything about master/slave status. For some reason I had it in my head the master/slave concept was just internal to Pacemaker and we could make whatever we wanted out of it.
> Hope this helps.
> Need help with High Availability?
> Pacemaker mailing list: Pacemaker [at] oss
> Project Home: http://www.clusterlabs.org
> Getting started:
> Bugs: http://bugs.clusterlabs.org
Pacemaker mailing list: Pacemaker [at] oss
Project Home: http://www.clusterlabs.org
Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf