From: Mikhail A Zelikov <mzelikov@cs.uml.edu>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] CMAN cluster event notification broken?
Date: Thu, 24 Aug 2006 11:49:58 -0400 (EDT) [thread overview]
Message-ID: <25090.128.221.197.129.1156434598.squirrel@webmail.cs.uml.edu> (raw)
I have a 2-node cluster, and I wrote a simple program that registers for
cluster events using:
cman_start_notification and cman_start_recv_data. If a node dies (manual
reboot/shutdown) then I receive CMAN_REASON_PORTCLOSED event and then NO
CMAN_REASON_STATECHANGE (as I woudl expect). I receive
CMAN_REASON_STATECHANGE once the node is booted again. If I do not
register for data then I do not receive CMAN_REASON_PORTCLOSED as
expected.
Is the notification mechanism broken?
Mike
P.S.
It also looks like that the conditions in while loop in cman_dispatch
might be incorrect if the intention was to continue forever as long as
there no errors.
while ( flags & CMAN_DISPATCH_ALL &&
(len < 0 && errno == EAGAIN) );
Should it be:
while ( flags & CMAN_DISPATCH_ALL &&
!(len < 0 && errno == EAGAIN) );
reply other threads:[~2006-08-24 15:49 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=25090.128.221.197.129.1156434598.squirrel@webmail.cs.uml.edu \
--to=mzelikov@cs.uml.edu \
/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).