[ClusterLabs] Pacemaker ordering constraints and resource failures

Devin A. Bougie devin.bougie at cornell.edu
Mon Aug 6 13:07:03 EDT 2018

What is the best way to make sure pacemaker doesn’t attempt to recover or restart a resource if a resource it depends on is not started?

For example, we have two dummy resources that simply sleep - master_sleep and slave_sleep.  We then have a non-symmetrical ordering constraint that ensures master_sleep is started before slave_sleep:
  start master_sleep then start slave_sleep (kind:Mandatory) (non-symmetrical)

This works as expected when both resources are disabled.  If we enable slave_sleep first, it won’t actually start until after master_sleep if enabled and started.

However, if slave_sleep dies when master_sleep is disabled and stopped, pacemaker recovers and restarts slave_sleep.  For example:
- enable master_sleep, and wait for it to start
- enable slave_sleep, and wait for it to start
- disable master_sleep, and wait for it to stop
- kill the slave_sleep process (or, “pcs resource debug-stop slave_sleep”)
- pacemaker recovers and restarts slave_sleep, even though master_sleep is disabled and stopped.

Is this the expected behavior, and is there any way to change it?  I’m happy to provide logs if that would help.

Many thanks,
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.clusterlabs.org/pipermail/users/attachments/20180806/c00df757/attachment.html>

More information about the Users mailing list