On 31/07/2013, at 11:47 AM, Jeff Frost <[email protected]> wrote: > > On Jul 30, 2013, at 6:34 PM, Andrew Beekhof <[email protected]> wrote: > >> >> On 27/07/2013, at 3:37 AM, Jeff Frost <[email protected]> wrote: >> >>> Is it possible when colocating a ping resource to avoid having the colocated >>> resource stopped if there is nowhere better to start it? >> >> Why would you colocate the ping resource with anything? >> Or do you mean location constraints that look for the attribute created by >> the ping resource? > > > Probably a terminology problem on my end.
:-) > I mean to colocate with a ping check score above a certain threshold and > that all works great, except when neither the master or the slave is able to > ping enough of the hosts, then pacemaker just stops them both, but I would > prefer to have them continue to replicate since they can still talk to one > another and neither host has a better ping score. > > I'm thinking the answer is it's not possible, but I just want to make sure. Sounds like Example 9.5 http://clusterlabs.org/doc/en-US/Pacemaker/1.1-pcs/html/Pacemaker_Explained/_tell_pacemaker_how_to_interpret_the_connectivity_data.html _______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
