[Pacemaker] Why location can't work as expected

[David Vossel]

----- Original Message -----
> Hello everyone:
> 
> my tools version
> pacemaker: 1.1.10
> corosync: 1.4.5
> crmsh-2.0
> 
> I have 2 nodes node1 and node2, resource agent Test must running on node1,
> and Test should not run on node2 if node1 is offline. So I do the following
> config:
> location TestOnNode1 Test INFINITY: node1
> 
> If node1 and node2 are both online, Test running on node1.
> But if node1 is offline, the resource agent Test will be switched to node2.
> I think that doesn't obey my config. My question:
> Is that pacemaker's feature? or I have missing some config?
> 
> I find the following config can work as expected:
> location TestOnNode1 Test -INFINITY: node2
> But I think that is not direct .

Yes, this is expected behavior.

Take a look at the symmetric-cluster option and learn about opt-in clusters here.

http://clusterlabs.org/doc/en-US/Pacemaker/1.1-pcs/html-single/Pacemaker_Explained/index.html#_asymmetrical_opt_in_clusters

-- Vossel


> thanks
> --
> 宝存科技 david
> 
> _______________________________________________
> Pacemaker mailing list: Pacemaker at oss.clusterlabs.org
> http://oss.clusterlabs.org/mailman/listinfo/pacemaker
> 
> Project Home: http://www.clusterlabs.org
> Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
> Bugs: http://bugs.clusterlabs.org
>