From: Lars Marowsky-Bree <lmb@suse.de>
To: Alex Aizman <itn780@yahoo.com>
Cc: Matt Mackall <mpm@selenic.com>,
linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [ANNOUNCE 0/6] Open-iSCSI High-Performance Initiator for Linux
Date: Thu, 10 Mar 2005 11:27:26 +0100 [thread overview]
Message-ID: <20050310102726.GT4105@marowsky-bree.de> (raw)
In-Reply-To: <422FB2B5.3070803@yahoo.com>
On 2005-03-09T18:36:37, Alex Aizman <itn780@yahoo.com> wrote:
> Heartbeat is good for reliability, etc. WRT "getting paged-out" -
> non-deterministic (things depend on time), right?
Right, if we didn't get scheduled often enough for us to send our
heartbeat messages to the other peers, they'll evict us from the cluster
and fence us, causing a service disruption.
With all these protections in place though, we can run at roughly 50ms
heartbeat intervals from user-space, reliably, which allows us a node
dead timer of ~200ms. I think that's pretty damn good.
(Of course, realistically, even for subsecond fail-over, 200ms keep
alives are sufficient, and 50ms would be quite extreme. But, it works.)
> >That works well in our current development series, and if you want to
> >share code, you can either rip it off (Open Source, we love ya ;) or we
> >can spin off these parts into a sub-package for you to depend on...
> If it's not a big deal :-) let's do the "sub-package" option.
I've brought this up on the linux-ha-dev list. When do you need this?
Sincerely,
Lars Marowsky-Brée <lmb@suse.de>
--
High Availability & Clustering
SUSE Labs, Research and Development
SUSE LINUX Products GmbH - A Novell Business
next prev parent reply other threads:[~2005-03-10 10:31 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-07 7:03 [ANNOUNCE 0/6] Open-iSCSI High-Performance Initiator for Linux Alex Aizman
2005-03-09 5:04 ` Matt Mackall
2005-03-09 5:51 ` Alex Aizman
2005-03-09 6:05 ` Matt Mackall
2005-03-09 6:25 ` Alex Aizman
2005-03-09 22:21 ` Lars Marowsky-Bree
2005-03-10 2:36 ` Alex Aizman
2005-03-10 10:27 ` Lars Marowsky-Bree [this message]
2005-03-11 7:00 ` Dmitry Yusupov
2005-03-09 6:25 ` Dmitry Yusupov
2005-03-09 6:50 ` Matt Mackall
2005-03-09 7:18 ` Dmitry Yusupov
[not found] <4229e34e.7e535078.5bc3.0b5eSMTPIN_ADDED@mx.googlegroups.com>
2005-03-06 1:02 ` Mike Christie
2005-03-12 16:55 ` Dave Wysochanski
2005-03-12 17:08 ` Dmitry Yusupov
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=20050310102726.GT4105@marowsky-bree.de \
--to=lmb@suse.de \
--cc=itn780@yahoo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=mpm@selenic.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