cluster-devel.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Fabio M. Di Nitto <fdinitto@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] cluster4 gfs_controld
Date: Fri, 14 Oct 2011 05:53:54 +0200	[thread overview]
Message-ID: <4E97B252.30107@redhat.com> (raw)
In-Reply-To: <4E974A55.3020300@redhat.com>

On 10/13/2011 10:30 PM, Lon Hohberger wrote:
> On 10/13/2011 11:30 AM, David Teigland wrote:
>> On Thu, Oct 13, 2011 at 03:41:31PM +0100, Steven Whitehouse wrote:
>>>> cluster4
>>>> . jid from dlm-kernel "slots" which will be assigned similarly
>>> What is the actual algorithm used to assign these slots?
>>
>> The same as picking jids: lowest unused id starting with 0.  As for
>> implementation, I'll add it to the current dlm recovery messages.
>>
>> (Frankly, I'd really like to just set jid to nodeid-1.  Any support for
>> that?  It would obviously add a slight requirement to picking nodeid's,
>> which 99.9% of people already do.)
> 
> While I think this is simple, I don't think this is the best idea.
> 
> This would only work efficiently if the cluster stack only used whole
> numbers, instead of say "integer" (like native corosync).


Doesn't pacemaker assigns random nodes ID in the 2^31 range? IIRC there
was a long debate at some point in the area. I am sure Andrew can shed
some light here.

Fabio



  reply	other threads:[~2011-10-14  3:53 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-13 14:20 [Cluster-devel] cluster4 gfs_controld David Teigland
2011-10-13 14:41 ` Steven Whitehouse
2011-10-13 15:30   ` David Teigland
2011-10-13 16:16     ` Steven Whitehouse
2011-10-13 16:49       ` David Teigland
2011-10-13 20:30     ` Lon Hohberger
2011-10-14  3:53       ` Fabio M. Di Nitto [this message]
2011-10-14  9:23         ` Andrew Beekhof
2011-10-13 15:02 ` Masatake YAMATO
2011-10-13 15:33   ` David Teigland
2011-10-13 19:00     ` Masatake YAMATO
2011-10-13 16:17   ` Steven Whitehouse

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=4E97B252.30107@redhat.com \
    --to=fdinitto@redhat.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).