From: Andrew Beekhof <andrew@beekhof.net>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [PATCH] dlm_controld.pcmk: Fix membership change judging issue
Date: Thu, 13 May 2010 22:19:58 +0200 [thread overview]
Message-ID: <AANLkTinW0yCHdfQOHpUecmLoQ4npmBqXAj1COlPndl1q@mail.gmail.com> (raw)
In-Reply-To: <20100513183215.GP20952@suse.de>
On Thu, May 13, 2010 at 8:32 PM, Lars Marowsky-Bree <lmb@novell.com> wrote:
> On 2010-05-13T18:25:42, Andrew Beekhof <andrew@beekhof.net> wrote:
>
>> >> ?void process_cluster(int ci)
>> >> ?{
>> >> - ? ?ais_dispatch(ais_fd_async, NULL);
>> >> ? ? ?update_cluster();
>> >> ?}
>> >
>> > Can this function be removed?
>>
>> No, it can't.
>> Remove that and the membership (and crm_peer_id_cache) stops being updated.
>>
>> Which makes me very suspicious of the whole patch because it clearly
>> wasn't tested very well.
>
> ais_dispatch() was moved to update_cluster(). That's safe, it seems.
But pointless and unrelated to the problem, so why include it?
> My question related to the detail that now process_cluster() is
> identical to update_cluster(), at initial reading suggesting the
> function might be redundant now.
process_cluster() and update_cluster() are both API entry points.
Does the behavior still occur with pacemaker 1.1.2?
next prev parent reply other threads:[~2010-05-13 20:19 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-13 8:49 [Cluster-devel] [PATCH] dlm_controld.pcmk: Fix membership change judging issue Jiaju Zhang
[not found] ` <20100513095117.GM20952@suse.de>
2010-05-13 10:18 ` Jiaju Zhang
2010-05-13 16:25 ` Andrew Beekhof
[not found] ` <20100513183215.GP20952@suse.de>
2010-05-13 20:19 ` Andrew Beekhof [this message]
2010-05-14 3:04 ` Tim Serong
2010-05-14 10:15 ` Andrew Beekhof
2010-05-14 11:28 ` Jiaju Zhang
[not found] ` <20100513203604.GQ20952@suse.de>
2010-05-14 9:52 ` Andrew Beekhof
2010-05-14 11:25 ` Jiaju Zhang
2010-05-14 4:08 ` Jiaju Zhang
2010-05-14 5:33 ` Jiaju Zhang
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=AANLkTinW0yCHdfQOHpUecmLoQ4npmBqXAj1COlPndl1q@mail.gmail.com \
--to=andrew@beekhof.net \
/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).