[Pacemaker] Simple way to prefer resource groups not start on the same node

Matthew Schlegel MSchlegel at x-iss.com
Wed Aug 25 11:30:39 EDT 2010

> -----Original Message-----
> From: Dejan Muhamedagic [mailto:dejanmm at fastmail.fm]
> Hi,
> On Tue, Aug 24, 2010 at 08:54:58AM -0500, Matthew Schlegel wrote:
> > Howdy,
> Pacemaker will try to balance the number of resources running on
> each node. Not perfect, but there's a good chance that no single
> node will run all the resources as you suggest.
> I think that doing location preferences is the right way to deal
> with this:
> location l-mysql1 mysql1 100: node1
> etc
> If node1 fails, mysql1 would move elsewhere. If the mysql1 fails,
> then you can use migration-threshold to control how many times to
> try to restart it. Use resource-stickiness to control when
> resources fail back.
> Finally, how often do you expect your resources/nodes to fail?
> Thanks,
> Dejan


In normal operations, I don't expect failures to occur very often.   One of the potential failure points would be power related, which would potentially take down half the nodes.

I have seen already that without any constraints applied, I end up with one node idle and two of the mysql resource groups running on one node.  Based on that, I'm hesitant to just let pacemaker completely do its own.

For now, I'll hook them up with location constraints to cover normal operation, and keep digging for a good way to handle balancing the resource groups in failure conditions.

Thank you,

Matthew Schlegel
System Analyst

eXcellence in IS Solutions, Inc. (X-ISS)
Office:  713.862.9200 x203

Making IT Work for You 
HPC & Enterprise IT Solutions

This message may contain privileged or otherwise confidential information.
If you are not the intended recipient, please immediately advise the sender
by reply email and delete the message and any attachments without using,
copying or disclosing the contents.

More information about the Pacemaker mailing list