cluster-devel.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Fabio Massimo Di Nitto <fabbione@ubuntu.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] spectator setting in cluster.conf
Date: Tue, 23 Oct 2007 23:07:01 +0200	[thread overview]
Message-ID: <471E6275.7040402@ubuntu.com> (raw)
In-Reply-To: <20071023181539.GC23832@redhat.com>

David Teigland wrote:
> On Tue, Oct 23, 2007 at 06:58:32PM +0200, Fabio Massimo Di Nitto wrote:
>>> An explicit votes= setting for a node would override the 0 votes implied
>>> by <spectator/>.
>> So ok. I need to understand you better because I think what I wrote
>> before is in contradiction with this override.
>>
>> In my patch spectator overrides votes="" no matter if they are specified
>> or not.
>>
>> Here you say that spectator overrides automatic setting of votes="" when
>> votes="" is not specified in the config. So in my head this implies two
>> config changes to set a node to spectator. Remove the votes="" entry (if
>> any and IME is quite common in the configs) and add spectator.
>>
>> I think it makes more sense (to me) to override votes="" in full when
>> spectator is set. 
> 
> If no votes are specified, the default is 1.  If no votes are specified
> and <spectator/> exists, then the default is 0.  If you want to override
> either of these defaults, then you include votes="N".  A specified value
> must always override a default value.

agreed :)

> If an existing cluster.conf has <clusternode ... votes="1">, the votes
> setting is obviously extraneous.  And making this node a full spectator
> would require either:
> 
> - changing to an explicit votes="0" and adding <spectator/>, or
> - removing the explicit votes setting altogether and adding <spectator/>

Ok perfect. That's all I wanted to agree on.

> It needs to be possible to have a spectator node with 1 vote (or more),
> and if you're saying that this config:
> 
>   <clusternode name="node1" nodeid="1" votes="1">
>     <spectator/>
>   </clusternode>
> 
> should *not* work to do that, then it's madness :-)

In my original proposal this snippet would have turned the node into a spectator
with <spectator/> having a higher priority over votes. That was all the origin
of my misunderstanding and I had to make sure we were on the same page.

Thanks for explaining over and over :)

Fabio

-- 
I'm going to make him an offer he can't refuse.



  reply	other threads:[~2007-10-23 21:07 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-22 15:12 [Cluster-devel] spectator setting in cluster.conf David Teigland
2007-10-23  5:25 ` Fabio Massimo Di Nitto
2007-10-23 13:45   ` David Teigland
2007-10-23 16:58     ` Fabio Massimo Di Nitto
2007-10-23 18:15       ` David Teigland
2007-10-23 21:07         ` Fabio Massimo Di Nitto [this message]
2007-10-24  3:37     ` Fabio Massimo Di Nitto
2007-10-24  6:36       ` Fabio Massimo Di Nitto

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=471E6275.7040402@ubuntu.com \
    --to=fabbione@ubuntu.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).