[Pacemaker] Pacemaker 1.0.8 and -INFINITY master score

Mon Aug 16 21:09:00 UTC 2010

Dejan,

Bug 2467 submitted.

I did place log messages in the agent to prove that the notification entry point 
is not called.

Thanks,

Bob

----- Original Message ----
From: Dejan Muhamedagic <dejanmm at fastmail.fm>
To: The Pacemaker cluster resource manager <pacemaker at oss.clusterlabs.org>
Sent: Mon, August 16, 2010 4:31:39 AM
Subject: Re: [Pacemaker] Pacemaker 1.0.8 and -INFINITY master score

Hi,

On Fri, Aug 13, 2010 at 06:00:28PM -0700, Bob Schatz wrote:
> Dejan,
> 
> I tested this with 1.0.9.1.   If a negative master score is set then it does 
>not 
>
> call promote.  Thanks!
> 
> However,  I still see notifications messages as shown below but it does not 
> appear that the actual notification entry point is called in the agent.
> If you agree, I will file a bug.

Yes, please, that looks strange. Are you sure that the agent is
not invoked?

> Aug 13 17:02:20 mgraid-MGG000090106M6T-0 pengine: [4463]: info: master_color: 
> ms-SSJ5AMGG000090106M6T: Promoted 0 instances of a possible 1 to master
> 
> Aug 13 17:03:34 mgraid-MGG000090106M6T-0 crmd: [1102]: info: te_rsc_command: 
> Initiating action 44: notify SSJ5AMGG000090106M6T:0_pre_notify_promote_0 on 
> mgraid-mgg000090106m6t-1
> 
> Aug 13 17:02:20 mgraid-MGG000090106M6T-0 pengine: [4463]: ERROR: 
> create_notification_boundaries: Creating boundaries for 
ms-SSJ5AMGG000090106M6T
> Aug 13 17:02:20 mgraid-MGG000090106M6T-0 pengine: [4463]: ERROR: 
> create_notification_boundaries: Creating boundaries for 
ms-SSJ5AMGG000090106M6T
> Aug 13 17:02:20 mgraid-MGG000090106M6T-0 pengine: [4463]: ERROR: 
> create_notification_boundaries: Creating boundaries for 
ms-SSJ5AMGG000090106M6T
> Aug 13 17:02:20 mgraid-MGG000090106M6T-0 pengine: [4463]: ERROR: 
> create_notification_boundaries: Creating boundaries for 
ms-SSJ5AMGG000090106M6T

I guess that these errors are a remnant of debugging sessions.

Thanks,

Dejan

> Aug 13 17:03:38 mgraid-MGG000090106M6T-0 crmd: [1102]: info: te_rsc_command: 
>Ini
> tiating action 8: promote SSJ5AMGG000090106M6T:0_promote_0 on 
>mgraid-mgg00009010
> 6m6t-1
> Aug 13 17:03:40 mgraid-MGG000090106M6T-0 crmd: [1102]: info: 
match_graph_event:
> Action SSJ5AMGG000090106M6T:0_promote_0 (8) confirmed on 
>mgraid-mgg000090106m6t-
> 1 (rc=0)
> Aug 13 17:03:41 mgraid-MGG000090106M6T-0 crmd: [1102]: info: te_rsc_command: 
>Ini
> tiating action 45: notify SSJ5AMGG000090106M6T:0_post_notify_promote_0 on 
>mgraid
> -mgg000090106m6t-1
> Aug 13 17:03:43 mgraid-MGG000090106M6T-0 crmd: [1102]: info: 
match_graph_event:
> Action SSJ5AMGG000090106M6T:0_post_notify_promote_0 (45) confirmed on 
>mgraid-mgg
> 000090106m6t-1 (rc=0)
> 
> 
> Thanks,
> 
> Bob
> 
> 
> 
> ----- Original Message ----
> From: Bob Schatz <bschatz at yahoo.com>
> To: The Pacemaker cluster resource manager <pacemaker at oss.clusterlabs.org>
> Sent: Fri, August 13, 2010 9:25:08 AM
> Subject: Re: [Pacemaker] Pacemaker 1.0.8 and -INFINITY master score
> 
> Dejan,
> 
> Thanks for the quick response!
> 
> Comments below with [BS]
> 
> ----- Original Message ----
> From: Dejan Muhamedagic <dejanmm at fastmail.fm>
> To: The Pacemaker cluster resource manager <pacemaker at oss.clusterlabs.org>
> Sent: Fri, August 13, 2010 3:03:49 AM
> Subject: Re: [Pacemaker] Pacemaker 1.0.8 and -INFINITY master score
> 
> Hi,
> 
> On Thu, Aug 12, 2010 at 12:54:10PM -0700, Bob Schatz wrote:
> > I upgraded to Pacemaker 1.0.8 since my application consists of Master/Slave 
> > resources and I wanted to pick up the fix for setting negative master 
scores.
> 
> Why not to 1.0.9.1?
> 
> 
> [BS] Because when I checked the 
> link http://www.clusterlabs.org/wiki/Get_Pacemaker 
>          it seemed to indicated that 1.0.8 was the last one fully tested with 
> the rest of the stack
>          (heartbeat, etc).   Are there fixes in 1.0.9 in this area?  I 
>generally 
>
> 
> am conservative about
> upgrading HA software until it has been out a while.  :)
> 
> > I am now able to set negative master scores when a resources starts and is 
> >SLAVE 
> >
> > but can't be promoted.  (The reason I want this is the process needs an 
> > administrative override and has to be up and running for the administrative 
> > override.)
> > 
> > However, when I test this on a one node cluster I see that the resource loops 
>
> > through the cycle (attempt promote, timeout, stop the resource, start the 
> > resource, ...).
> > 
> > I would have thought that a master score of -INFINITY would have prevented 
>the 
>
> 
> 
> > promotion.
> 
> Yes, sounds like it. Where is the score set? Wouldn't "resource
> demote" do the right thing?
> 
> [BS] I used the ~October 2009 DRBD agent as a reference.  The "crm_master -Q -l 
>
> reboot -v -10"
>         call is made at the end of the start() entry point in the agent.
>          I am not sure what you mean by "resource demote"
> 
> > My configuration is:
> > 
> > node $id="f4e5e15c-d06b-4e37-89b9-4621af05128f" mgraid-bob00001-0
> > primitive SSJ5AMKP00009010REPK ocf:omneon:ss \
> >     params ss_resource="SSJ5AMKP00009010REPK" 
> > ssconf="/var/omneon/config/config.J5AMKP00009010REPK" \
> >     op monitor interval="3s" role="Master" timeout="7s" \
> >     op monitor interval="10s" role="Slave" timeout="7" \
> >     op stop interval="0" timeout="100" \
> >     op start interval="0" timeout="120" \
> >     meta id="SSJ5AMKP00009010REPK-meta_attributes"
> > ms ms-SSJ5AMKP00009010REPK SSJ5AMKP00009010REPK \
> >     meta clone-max="2" notify="true" globaally-unique="false" 
> 
> You have a typo here.
> 
> [BS] AH!!!  I owe you at least one drink for that!!!
> 
> 
> Thanks,
> 
> Bob
> 
> Thanks,
> 
> Dejan
> 
> > target-role="Master"
> > location ms-SSJ5AMKP00009010REPK-master-w1 ms-SSJ5AMKP00009010REPK \
> >     rule $id="ms-SSJ5AMKP00009010REPK-master-w1-rule" $role="master" 100: 
> >#uname 
> >
> > eq mgraid-BOB00001-0
> > property $id="cib-bootstrap-options" \
> >     dc-version="1.0.8-9881a7350d6182bae9e8e557cf20a3cc5dac3ee7" \
> >     cluster-infrastructure="Heartbeat" \
> >     stonith-enabled="false"
> > 
> > Is this the expected behavior?
> > 
> > 
> > Thanks,
> > 
> > Bob
> > 
> > 
> > 
> >      
> > 
> > 
> > _______________________________________________
> > 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
> 
> 
> 
>      
> 
> 
> _______________________________________________
> 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

_______________________________________________
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