From: Fabio M. Di NItto <fabbione@fabbione.net>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [PATCH] Fix pacemaker's wrong quorum view in a CMAN+pacemaker cluster
Date: Sun, 13 Mar 2011 15:34:49 +0100 [thread overview]
Message-ID: <4D7CD609.6060003@fabbione.net> (raw)
In-Reply-To: <4D7CC3D1.7080600@gmail.com>
On 03/13/2011 02:17 PM, Simone Gotti wrote:
>
> The fix I tried used CMAN_DISPATCH_ALL instead of CMAN_DISPATCH_ONE and
> looks like its working.
In most of our cluster daemons, we use DISPATCH_ONE in a proper loop to
be repeated till there are no more events in the queue.
I don't recall exactly why one is better than another tho. That would
require some investigation in libcman.
Fabio
next prev parent reply other threads:[~2011-03-13 14:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-13 13:17 [Cluster-devel] [PATCH] Fix pacemaker's wrong quorum view in a CMAN+pacemaker cluster Simone Gotti
2011-03-13 14:34 ` Fabio M. Di NItto [this message]
2011-03-14 7:36 ` Andrew Beekhof
2011-03-14 10:04 ` Simone Gotti
2011-03-14 10:41 ` Andrew Beekhof
2011-03-14 15:37 ` Simone Gotti
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=4D7CD609.6060003@fabbione.net \
--to=fabbione@fabbione.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).