cluster-devel.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Fabio M. Di Nitto <fdinitto@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] SCTP versus OpenAIS/corosync time-outs
Date: Thu, 05 Nov 2009 08:23:59 +0100	[thread overview]
Message-ID: <4AF27D8F.9090207@redhat.com> (raw)
In-Reply-To: <20091104212941.GD32760@suse.de>

Lars Marowsky-Bree wrote:
> On 2009-11-02T08:41:43, Christine Caulfield <ccaulfie@redhat.com> wrote:
> 
> A quite different trick for redundant networking would be to assign
> static addresses to lo:X and run OSPF over all links, and having DLM
> connect to the static IPs. That's quite trivial to setup, give us
> "resilient" TCP (w/o needing to mess with SCTP, bonding, or anything).
> 
> Comments?
> 

OSPF timings to converge networks can be very long as it involves link
UP/DOWN events, flapping protection and so on and so forth... IMHO,
while the idea is valid, it introduces a new whole set of timeouts to
take into account.

IMHO it?s a lot simpler to do something like this:

monitor the links status, if UP assign a static route with different
metric so that one link is always preferred over another. On link DOWN
event, remove the static route, flush the route cache (speed up kernel
look ups into the new route with higher or lower metric), and traffic
will flow very quickly again on the new link.

I use a very similar setup using a patched version of vtun (we clearly
don?t want or need that), and the response time is in the order of a
couple of seconds (it could be a lot lower with proper trimming to the
setup).

Fabio



      reply	other threads:[~2009-11-05  7:23 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-31  0:20 [Cluster-devel] SCTP versus OpenAIS/corosync time-outs Lars Marowsky-Bree
2009-11-02  8:41 ` Christine Caulfield
2009-11-02 16:37   ` David Teigland
2009-11-04 21:29   ` Lars Marowsky-Bree
2009-11-05  7:23     ` Fabio M. Di Nitto [this message]

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=4AF27D8F.9090207@redhat.com \
    --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).