Re: [Pacemaker] colocation issue with master-slave resources
On Tue, Nov 29, 2011 at 10:10 AM, Patrick H. wrote: > Upgraded to 1.1.6 and put in an ordering constraint, still no joy. Could you file a bug and include a crm_report for this please? > > # crm status > > Last updated: Mon Nov 28 23:09:37 2011 > Last change: Mon Nov 28 23:08:34 2011 via cibadmin on devlvs03 > > Stack: cman > Current DC: devlvs03 - partition with quorum > Version: 1.1.6-1.el6-b379478e0a66af52708f56d0302f50b6f13322bd > > 2 Nodes configured, 2 expected votes > 5 Resources configured. > > > Online: [ devlvs04 devlvs03 ] > > dummy (ocf::pacemaker:Dummy): Started devlvs03 > Master/Slave Set: stateful1-ms [stateful1] > Masters: [ devlvs04 ] > Slaves: [ devlvs03 ] > Master/Slave Set: stateful2-ms [stateful2] > Masters: [ devlvs04 ] > Slaves: [ devlvs03 ] > > > # crm configure show > node devlvs03 \ > attributes standby="off" > node devlvs04 \ > attributes standby="off" > primitive dummy ocf:pacemaker:Dummy \ > meta target-role="Started" > primitive stateful1 ocf:pacemaker:Stateful > primitive stateful2 ocf:pacemaker:Stateful > ms stateful1-ms stateful1 > ms stateful2-ms stateful2 > colocation stateful1-colocation inf: stateful1-ms:Master dummy:Started > colocation stateful2-colocation inf: stateful2-ms:Master dummy:Started > order stateful1-start inf: dummy:start stateful1-ms:promote > order stateful2-start inf: dummy:start stateful2-ms:promote > property $id="cib-bootstrap-options" \ > dc-version="1.1.6-1.el6-b379478e0a66af52708f56d0302f50b6f13322bd" \ > > cluster-infrastructure="cman" \ > expected-quorum-votes="2" \ > stonith-enabled="false" \ > no-quorum-policy="ignore" \ > last-lrm-refresh="1322450542" ___ Pacemaker mailing list: Pacemaker@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
Re: [Pacemaker] colocation issue with master-slave resources
Sent: Mon Nov 28 2011 16:10:01 GMT-0700 (MST) From: Patrick H. To: The Pacemaker cluster resource manager Andreas Kurz Subject: Re: [Pacemaker] colocation issue with master-slave resources Sent: Mon Nov 28 2011 15:27:10 GMT-0700 (MST) From: Andrew Beekhof To: The Pacemaker cluster resource manager Andreas Kurz Subject: Re: [Pacemaker] colocation issue with master-slave resources Perhaps try and ordering constraint, I may have also fixed something in this area for 1.1.6 so an upgrade might also help On Tue, Nov 29, 2011 at 1:38 AM, Patrick H. wrote: Sent: Mon Nov 28 2011 01:31:22 GMT-0700 (MST) From: Andreas Kurz To: The Pacemaker cluster resource manager Subject: Re: [Pacemaker] colocation issue with master-slave resources On 11/28/2011 04:51 AM, Patrick H. wrote: I'm trying to setup a colocation rule so that a couple of master-slave resources cant be master unless another resource is running on the same node, and am getting the exact opposite of what I want. The master-slave resources are getting promoted to master on the node which this other resource isnt running on. In the below example, 'stateful1:Master' and 'stateful2:Master' should be on the same node 'dummy' is on. It works just fine if I change the colocation around so that 'dummy' depends on the stateful resources being master, but I dont want that. I want dummy to be able to run no matter what, but the stateful resources not be able to become master without dummy. # crm status Last updated: Mon Nov 28 03:47:04 2011 Stack: cman Current DC: devlvs03 - partition with quorum Version: 1.1.5-5.el6-01e86afaaa6d4a8c4836f68df80ababd6ca3902f 2 Nodes configured, 2 expected votes 6 Resources configured. Online: [ devlvs04 devlvs03 ] dummy(ocf::pacemaker:Dummy):Started devlvs03 Master/Slave Set: stateful1-ms [stateful1] Masters: [ devlvs04 ] Slaves: [ devlvs03 ] Master/Slave Set: stateful2-ms [stateful2] Masters: [ devlvs04 ] Slaves: [ devlvs03 ] # crm configure show node devlvs03 \ attributes standby="off" node devlvs04 \ attributes standby="off" primitive dummy ocf:pacemaker:Dummy \ meta target-role="Started" primitive stateful1 ocf:pacemaker:Stateful primitive stateful2 ocf:pacemaker:Stateful ms stateful1-ms stateful1 ms stateful2-ms stateful2 colocation stateful1-colocation inf: stateful1-ms:Master dummy colocation stateful2-colocation inf: stateful2-ms:Master dummy use dummy:Started ... default is to use same role as left resource, and Dummy will never be in role Master ... Regards, Andreas Tried that too (just not the configuration at the time I sent the email), no effect. Upgraded to 1.1.6 and put in an ordering constraint, still no joy. # crm status Last updated: Mon Nov 28 23:09:37 2011 Last change: Mon Nov 28 23:08:34 2011 via cibadmin on devlvs03 Stack: cman Current DC: devlvs03 - partition with quorum Version: 1.1.6-1.el6-b379478e0a66af52708f56d0302f50b6f13322bd 2 Nodes configured, 2 expected votes 5 Resources configured. Online: [ devlvs04 devlvs03 ] dummy(ocf::pacemaker:Dummy):Started devlvs03 Master/Slave Set: stateful1-ms [stateful1] Masters: [ devlvs04 ] Slaves: [ devlvs03 ] Master/Slave Set: stateful2-ms [stateful2] Masters: [ devlvs04 ] Slaves: [ devlvs03 ] # crm configure show node devlvs03 \ attributes standby="off" node devlvs04 \ attributes standby="off" primitive dummy ocf:pacemaker:Dummy \ meta target-role="Started" primitive stateful1 ocf:pacemaker:Stateful primitive stateful2 ocf:pacemaker:Stateful ms stateful1-ms stateful1 ms stateful2-ms stateful2 colocation stateful1-colocation inf: stateful1-ms:Master dummy:Started colocation stateful2-colocation inf: stateful2-ms:Master dummy:Started order stateful1-start inf: dummy:start stateful1-ms:promote order stateful2-start inf: dummy:start stateful2-ms:promote property $id="cib-bootstrap-options" \ dc-version="1.1.6-1.el6-b379478e0a66af52708f56d0302f50b6f13322bd" \ cluster-infrastructure="cman" \ expected-quorum-votes="2" \ stonith-enabled="false" \ no-quorum-policy="ignore" \ last-lrm-refresh="1322450542" Well there is a really ugly workaround that solves this. If I convert 'dummy' to a master-slave resource, and just have the slave do nothing. It does obey the colocation rule when I tell it to keep the Master roles on the same box. ___ Pacemaker mailing list: Pacemaker@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
Re: [Pacemaker] colocation issue with master-slave resources
Sent: Mon Nov 28 2011 15:27:10 GMT-0700 (MST) From: Andrew Beekhof To: The Pacemaker cluster resource manager Andreas Kurz Subject: Re: [Pacemaker] colocation issue with master-slave resources Perhaps try and ordering constraint, I may have also fixed something in this area for 1.1.6 so an upgrade might also help On Tue, Nov 29, 2011 at 1:38 AM, Patrick H. wrote: Sent: Mon Nov 28 2011 01:31:22 GMT-0700 (MST) From: Andreas Kurz To: The Pacemaker cluster resource manager Subject: Re: [Pacemaker] colocation issue with master-slave resources On 11/28/2011 04:51 AM, Patrick H. wrote: I'm trying to setup a colocation rule so that a couple of master-slave resources cant be master unless another resource is running on the same node, and am getting the exact opposite of what I want. The master-slave resources are getting promoted to master on the node which this other resource isnt running on. In the below example, 'stateful1:Master' and 'stateful2:Master' should be on the same node 'dummy' is on. It works just fine if I change the colocation around so that 'dummy' depends on the stateful resources being master, but I dont want that. I want dummy to be able to run no matter what, but the stateful resources not be able to become master without dummy. # crm status Last updated: Mon Nov 28 03:47:04 2011 Stack: cman Current DC: devlvs03 - partition with quorum Version: 1.1.5-5.el6-01e86afaaa6d4a8c4836f68df80ababd6ca3902f 2 Nodes configured, 2 expected votes 6 Resources configured. Online: [ devlvs04 devlvs03 ] dummy(ocf::pacemaker:Dummy):Started devlvs03 Master/Slave Set: stateful1-ms [stateful1] Masters: [ devlvs04 ] Slaves: [ devlvs03 ] Master/Slave Set: stateful2-ms [stateful2] Masters: [ devlvs04 ] Slaves: [ devlvs03 ] # crm configure show node devlvs03 \ attributes standby="off" node devlvs04 \ attributes standby="off" primitive dummy ocf:pacemaker:Dummy \ meta target-role="Started" primitive stateful1 ocf:pacemaker:Stateful primitive stateful2 ocf:pacemaker:Stateful ms stateful1-ms stateful1 ms stateful2-ms stateful2 colocation stateful1-colocation inf: stateful1-ms:Master dummy colocation stateful2-colocation inf: stateful2-ms:Master dummy use dummy:Started ... default is to use same role as left resource, and Dummy will never be in role Master ... Regards, Andreas Tried that too (just not the configuration at the time I sent the email), no effect. Upgraded to 1.1.6 and put in an ordering constraint, still no joy. # crm status Last updated: Mon Nov 28 23:09:37 2011 Last change: Mon Nov 28 23:08:34 2011 via cibadmin on devlvs03 Stack: cman Current DC: devlvs03 - partition with quorum Version: 1.1.6-1.el6-b379478e0a66af52708f56d0302f50b6f13322bd 2 Nodes configured, 2 expected votes 5 Resources configured. Online: [ devlvs04 devlvs03 ] dummy(ocf::pacemaker:Dummy):Started devlvs03 Master/Slave Set: stateful1-ms [stateful1] Masters: [ devlvs04 ] Slaves: [ devlvs03 ] Master/Slave Set: stateful2-ms [stateful2] Masters: [ devlvs04 ] Slaves: [ devlvs03 ] # crm configure show node devlvs03 \ attributes standby="off" node devlvs04 \ attributes standby="off" primitive dummy ocf:pacemaker:Dummy \ meta target-role="Started" primitive stateful1 ocf:pacemaker:Stateful primitive stateful2 ocf:pacemaker:Stateful ms stateful1-ms stateful1 ms stateful2-ms stateful2 colocation stateful1-colocation inf: stateful1-ms:Master dummy:Started colocation stateful2-colocation inf: stateful2-ms:Master dummy:Started order stateful1-start inf: dummy:start stateful1-ms:promote order stateful2-start inf: dummy:start stateful2-ms:promote property $id="cib-bootstrap-options" \ dc-version="1.1.6-1.el6-b379478e0a66af52708f56d0302f50b6f13322bd" \ cluster-infrastructure="cman" \ expected-quorum-votes="2" \ stonith-enabled="false" \ no-quorum-policy="ignore" \ last-lrm-refresh="1322450542" ___ Pacemaker mailing list: Pacemaker@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
Re: [Pacemaker] colocation issue with master-slave resources
Perhaps try and ordering constraint, I may have also fixed something in this area for 1.1.6 so an upgrade might also help On Tue, Nov 29, 2011 at 1:38 AM, Patrick H. wrote: > Sent: Mon Nov 28 2011 01:31:22 GMT-0700 (MST) > From: Andreas Kurz > To: The Pacemaker cluster resource manager > Subject: Re: [Pacemaker] colocation issue with master-slave resources > > On 11/28/2011 04:51 AM, Patrick H. wrote: > > I'm trying to setup a colocation rule so that a couple of master-slave > resources cant be master unless another resource is running on the same > node, and am getting the exact opposite of what I want. The master-slave > resources are getting promoted to master on the node which this other > resource isnt running on. > > In the below example, 'stateful1:Master' and 'stateful2:Master' should > be on the same node 'dummy' is on. It works just fine if I change the > colocation around so that 'dummy' depends on the stateful resources > being master, but I dont want that. I want dummy to be able to run no > matter what, but the stateful resources not be able to become master > without dummy. > > > # crm status > > Last updated: Mon Nov 28 03:47:04 2011 > Stack: cman > Current DC: devlvs03 - partition with quorum > Version: 1.1.5-5.el6-01e86afaaa6d4a8c4836f68df80ababd6ca3902f > 2 Nodes configured, 2 expected votes > 6 Resources configured. > > > Online: [ devlvs04 devlvs03 ] > > dummy(ocf::pacemaker:Dummy):Started devlvs03 > Master/Slave Set: stateful1-ms [stateful1] > Masters: [ devlvs04 ] > Slaves: [ devlvs03 ] > Master/Slave Set: stateful2-ms [stateful2] > Masters: [ devlvs04 ] > Slaves: [ devlvs03 ] > > > # crm configure show > node devlvs03 \ > attributes standby="off" > node devlvs04 \ > attributes standby="off" > primitive dummy ocf:pacemaker:Dummy \ > meta target-role="Started" > primitive stateful1 ocf:pacemaker:Stateful > primitive stateful2 ocf:pacemaker:Stateful > ms stateful1-ms stateful1 > ms stateful2-ms stateful2 > colocation stateful1-colocation inf: stateful1-ms:Master dummy > colocation stateful2-colocation inf: stateful2-ms:Master dummy > > use dummy:Started ... default is to use same role as left resource, and > Dummy will never be in role Master ... > > Regards, > Andreas > > Tried that too (just not the configuration at the time I sent the email), no > effect. > > ___ > Pacemaker mailing list: Pacemaker@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 > > ___ Pacemaker mailing list: Pacemaker@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
Re: [Pacemaker] colocation issue with master-slave resources
Sent: Mon Nov 28 2011 01:31:22 GMT-0700 (MST) From: Andreas Kurz To: The Pacemaker cluster resource manager Subject: Re: [Pacemaker] colocation issue with master-slave resources On 11/28/2011 04:51 AM, Patrick H. wrote: I'm trying to setup a colocation rule so that a couple of master-slave resources cant be master unless another resource is running on the same node, and am getting the exact opposite of what I want. The master-slave resources are getting promoted to master on the node which this other resource isnt running on. In the below example, 'stateful1:Master' and 'stateful2:Master' should be on the same node 'dummy' is on. It works just fine if I change the colocation around so that 'dummy' depends on the stateful resources being master, but I dont want that. I want dummy to be able to run no matter what, but the stateful resources not be able to become master without dummy. # crm status Last updated: Mon Nov 28 03:47:04 2011 Stack: cman Current DC: devlvs03 - partition with quorum Version: 1.1.5-5.el6-01e86afaaa6d4a8c4836f68df80ababd6ca3902f 2 Nodes configured, 2 expected votes 6 Resources configured. Online: [ devlvs04 devlvs03 ] dummy(ocf::pacemaker:Dummy):Started devlvs03 Master/Slave Set: stateful1-ms [stateful1] Masters: [ devlvs04 ] Slaves: [ devlvs03 ] Master/Slave Set: stateful2-ms [stateful2] Masters: [ devlvs04 ] Slaves: [ devlvs03 ] # crm configure show node devlvs03 \ attributes standby="off" node devlvs04 \ attributes standby="off" primitive dummy ocf:pacemaker:Dummy \ meta target-role="Started" primitive stateful1 ocf:pacemaker:Stateful primitive stateful2 ocf:pacemaker:Stateful ms stateful1-ms stateful1 ms stateful2-ms stateful2 colocation stateful1-colocation inf: stateful1-ms:Master dummy colocation stateful2-colocation inf: stateful2-ms:Master dummy use dummy:Started ... default is to use same role as left resource, and Dummy will never be in role Master ... Regards, Andreas Tried that too (just not the configuration at the time I sent the email), no effect. ___ Pacemaker mailing list: Pacemaker@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
Re: [Pacemaker] colocation issue with master-slave resources
On 11/28/2011 04:51 AM, Patrick H. wrote: > I'm trying to setup a colocation rule so that a couple of master-slave > resources cant be master unless another resource is running on the same > node, and am getting the exact opposite of what I want. The master-slave > resources are getting promoted to master on the node which this other > resource isnt running on. > > In the below example, 'stateful1:Master' and 'stateful2:Master' should > be on the same node 'dummy' is on. It works just fine if I change the > colocation around so that 'dummy' depends on the stateful resources > being master, but I dont want that. I want dummy to be able to run no > matter what, but the stateful resources not be able to become master > without dummy. > > > # crm status > > Last updated: Mon Nov 28 03:47:04 2011 > Stack: cman > Current DC: devlvs03 - partition with quorum > Version: 1.1.5-5.el6-01e86afaaa6d4a8c4836f68df80ababd6ca3902f > 2 Nodes configured, 2 expected votes > 6 Resources configured. > > > Online: [ devlvs04 devlvs03 ] > > dummy(ocf::pacemaker:Dummy):Started devlvs03 > Master/Slave Set: stateful1-ms [stateful1] > Masters: [ devlvs04 ] > Slaves: [ devlvs03 ] > Master/Slave Set: stateful2-ms [stateful2] > Masters: [ devlvs04 ] > Slaves: [ devlvs03 ] > > > # crm configure show > node devlvs03 \ > attributes standby="off" > node devlvs04 \ > attributes standby="off" > primitive dummy ocf:pacemaker:Dummy \ > meta target-role="Started" > primitive stateful1 ocf:pacemaker:Stateful > primitive stateful2 ocf:pacemaker:Stateful > ms stateful1-ms stateful1 > ms stateful2-ms stateful2 > colocation stateful1-colocation inf: stateful1-ms:Master dummy > colocation stateful2-colocation inf: stateful2-ms:Master dummy use dummy:Started ... default is to use same role as left resource, and Dummy will never be in role Master ... Regards, Andreas -- Need help with Pacemaker? http://www.hastexo.com/now > property $id="cib-bootstrap-options" \ > dc-version="1.1.5-5.el6-01e86afaaa6d4a8c4836f68df80ababd6ca3902f" \ > cluster-infrastructure="cman" \ > expected-quorum-votes="2" \ > stonith-enabled="false" \ > no-quorum-policy="ignore" \ > last-lrm-refresh="1322450542" > > > ___ > Pacemaker mailing list: Pacemaker@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 signature.asc Description: OpenPGP digital signature ___ Pacemaker mailing list: Pacemaker@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
[Pacemaker] colocation issue with master-slave resources
I'm trying to setup a colocation rule so that a couple of master-slave resources cant be master unless another resource is running on the same node, and am getting the exact opposite of what I want. The master-slave resources are getting promoted to master on the node which this other resource isnt running on. In the below example, 'stateful1:Master' and 'stateful2:Master' should be on the same node 'dummy' is on. It works just fine if I change the colocation around so that 'dummy' depends on the stateful resources being master, but I dont want that. I want dummy to be able to run no matter what, but the stateful resources not be able to become master without dummy. # crm status Last updated: Mon Nov 28 03:47:04 2011 Stack: cman Current DC: devlvs03 - partition with quorum Version: 1.1.5-5.el6-01e86afaaa6d4a8c4836f68df80ababd6ca3902f 2 Nodes configured, 2 expected votes 6 Resources configured. Online: [ devlvs04 devlvs03 ] dummy(ocf::pacemaker:Dummy):Started devlvs03 Master/Slave Set: stateful1-ms [stateful1] Masters: [ devlvs04 ] Slaves: [ devlvs03 ] Master/Slave Set: stateful2-ms [stateful2] Masters: [ devlvs04 ] Slaves: [ devlvs03 ] # crm configure show node devlvs03 \ attributes standby="off" node devlvs04 \ attributes standby="off" primitive dummy ocf:pacemaker:Dummy \ meta target-role="Started" primitive stateful1 ocf:pacemaker:Stateful primitive stateful2 ocf:pacemaker:Stateful ms stateful1-ms stateful1 ms stateful2-ms stateful2 colocation stateful1-colocation inf: stateful1-ms:Master dummy colocation stateful2-colocation inf: stateful2-ms:Master dummy property $id="cib-bootstrap-options" \ dc-version="1.1.5-5.el6-01e86afaaa6d4a8c4836f68df80ababd6ca3902f" \ cluster-infrastructure="cman" \ expected-quorum-votes="2" \ stonith-enabled="false" \ no-quorum-policy="ignore" \ last-lrm-refresh="1322450542" ___ Pacemaker mailing list: Pacemaker@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
