[ClusterLabs] resource on remote node not failing over

David Vossel dvossel at redhat.com
Fri Mar 13 19:21:13 EDT 2015

----- Original Message -----
> Hi
> I have a two node cluster (Centos6.6/Pacemaker 1.1.12/Cman/Corosync 1.4.7)
> It is an asymmetric cluster (symmetric-cluster: false)
> There are two VM's (running Centos) in the cluster acting as remote
> nodes (lx16mx & lx17mx). These are on drbd backing storage.
> Other VM's (running other services) will be added in due course.
> Bind named service is installed/configured on both remote nodes, will
> start up on both nodes, and is being managed by an RA (ocf:heartbeat:named).
> I have location constraints to allow the resource to run on these nodes
> and I can move this resource between these nodes.
> However, if I disable the named service on the live node (by renaming
> the main config file and shutting down service), the resource does not
> failover to the other remote node.

Is pacemaker detecting this as a failure? I would expect pacemaker to 
attempt to recover the dns server on the node it failed on first. If the
dns server can't be started on that node I'd expect it to fail over somewhere

> As an aside, is there any difference in the effect of these two commands:
>      pcs constraint location add location_drbd-lx16-node1 drbd-lx16
> ukdenavhost1 500
>      pcs constraint location drbd-lx16 rule  score=500 \#uname eq
> "ukdenavhost1"

should be the same thing.

> pcs config and status attached. I can send logs if required.
> Thanks.
> _______________________________________________
> Users mailing list: Users at clusterlabs.org
> http://clusterlabs.org/mailman/listinfo/users
> Project Home: http://www.clusterlabs.org
> Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
> Bugs: http://bugs.clusterlabs.org

More information about the Users mailing list