From: Fabio M. Di Nitto <fdinitto@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [RFC] Common cluster connection handler API
Date: Fri, 27 Jun 2008 20:19:36 +0200 (CEST) [thread overview]
Message-ID: <Pine.LNX.4.64.0806272016570.27368@trider-g7> (raw)
In-Reply-To: <20080627163538.GC19105@redhat.com>
On Fri, 27 Jun 2008, David Teigland wrote:
> On Fri, Jun 27, 2008 at 07:26:09AM +0200, Fabio M. Di Nitto wrote:
>> connect to ccs
>> connect to cman
>> wait for cman_is_active
>> return 0 on success, < 0 otherwise if we fail to connect within
>> max_attempts or blocking is set to 0.. or any other error for the matter.
>
> I'm not in favor of another layer, let's just fix things up where needed.
that's virtually in every tool/daemon. I don't see this as a real layer.
Just a simple helper to do it right everywhere.
> I was actually hoping that with no more ccsd there'd be no more
> "connecting" to ccs, but that's probably a topic for one of the ccs
> meetings...
The only partial advantage you have, as i documented and wrote to
cluster-devel, is that if you are connected to cman and cman_is_active,
you are guaranteed 99.9% to connected to ccs without problems (only
reason for rejection would be lack of resources on the machine, but at
that point you have more serious issues to worry about).
Fabio
--
I'm going to make him an offer he can't refuse.
next prev parent reply other threads:[~2008-06-27 18:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-27 5:26 [Cluster-devel] [RFC] Common cluster connection handler API Fabio M. Di Nitto
2008-06-27 16:35 ` David Teigland
2008-06-27 18:19 ` Fabio M. Di Nitto [this message]
2008-06-27 19:27 ` David Teigland
2008-06-28 4:58 ` Fabio M. Di Nitto
2008-06-28 5:01 ` Fabio M. 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=Pine.LNX.4.64.0806272016570.27368@trider-g7 \
--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).