[Pacemaker] colocation and ordering for groups/clones/instances

Andrew Beekhof andrew at beekhof.net
Thu Oct 6 18:15:07 EDT 2011


On Fri, Oct 7, 2011 at 5:01 AM, gustavo panizzo <gfa> <gfa at zumbi.com.ar> wrote:
> i fix my ordering problems using fully explicit order "chains"
>
> colocation col_db0005 +inf: HASI ora-bkp vgoradb vgoralog db0005-storage db0005-db db0005-ip
> order ord_db0005 +inf: HASI ora-bkp vgoradb vgoralog db0005-storage db0005-db db0005-ip
>
> it really works, crm configure verify give OK.
> but i cannot found any reference to this on the documentation,

look for resource sets

> it is supported?
> will it be supported in the future?

yes

>
> thanks
>
> On Thu, Oct 06, 2011 at 02:01:42PM +1100, Andrew Beekhof wrote:
>> On Thu, Oct 6, 2011 at 2:47 AM, gustavo panizzo <gfa> <gfa at zumbi.com.ar> wrote:
>> > On Wed, Oct 05, 2011 at 10:45:32AM +1100, Andrew Beekhof wrote:
>> >> On Wed, Oct 5, 2011 at 10:21 AM, gustavo panizzo <gfa> <gfa at zumbi.com.ar> wrote:
>> >> > colocation col_name +inf: clone2 clone
>> >> > colocation col_name +inf: group clone2
>>
>> also doesn't do what you think. don't create colocation loops.
>> pretty sure you just want:
>>    colocation col_name +inf: group clone2
>>
>> >> > order ord_name +inf: clone2 group symmetrical=false
>> >> > order ord_name +inf: clone clone2 symmetrical=false
>> >>
>> >> drop the symmetrical=false parts
>> > why? the oposite order won't work (VG before clvm)
>>
>> it doesn't mean the opposite for starts.  "clone2 group" means start
>> clone2 before starting group and stop group before stopping clone2
>>
>> > i've dropped it and the issue still happening
>> >
>> >>
>> >> >
>> >> >
>> >> > when i restart a machine (not the one with RG on it), clone starts on it
>> >> > RG gets stopped where is running until clone is fully up
>> >>
>> >> that doesn't sound right. can you include the result of cibadmin -Ql
>> >> when the cluster is in this state?
>> > attached, in this moment node2 is entering the cluster, and the
>> > resource group qsprod (it was running) went down partially
>>
>> I'll have a look in a bit
>>
>> >
>> > thanks
>> >>
>> > --
>> > 1AE0 322E B8F7 4717 BDEA  BF1D 44BB 1BA7 9F6C 6333
>> >
>> >
>> > _______________________________________________
>> > 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://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker
>> >
>> >
>>
>> _______________________________________________
>> 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://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker
>
> --
> 1AE0 322E B8F7 4717 BDEA  BF1D 44BB 1BA7 9F6C 6333
>
>
> _______________________________________________
> 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://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker
>




More information about the Pacemaker mailing list