linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Paul Clements <paul.clements@steeleye.com>
To: Dan Stromberg <strombrg@dcs.nac.uci.edu>
Cc: linux-raid@vger.kernel.org
Subject: Re: active/active vs active/passive?
Date: Tue, 07 Jun 2005 20:54:36 -0400	[thread overview]
Message-ID: <42A641CC.9040905@steeleye.com> (raw)
In-Reply-To: <1118189397.15459.108.camel@seki.nac.uci.edu>

Dan Stromberg wrote:
> The lecturer at the recent NG storage talk at Usenix in Anaheim,
> indicated that it was best to avoid "active/active" and get
> "active/passive" instead.
> 
> Does anyone:
> 
> 1) Know what these things mean?

In the clustering world, active/active means 2 or more servers are 
active at a time, either operating on separate data (and thus acting as 
passive failover partners to each other), or operating on the same data 
(which requires the use of a cluster filesystem or other similar 
mechanism to allow coherent simultaneous access to the data).

> 2) Know why active/passive might be preferred over active/active?

Well, if you're talking about active/passive vs. active/active with a 
cluster filesystem or such, the active/passive is tons easier to 
implement and get right. Plus, depending on your application, the added 
complexity of a cluster filesystem might not actually buy you much more 
than you could get with, say, NFS or Samba (CIFS).

--
Paul

  parent reply	other threads:[~2005-06-08  0:54 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-08  0:09 active/active vs active/passive? Dan Stromberg
2005-06-08  0:16 ` Neil Brown
2005-06-08 17:07   ` Dan Stromberg
2005-06-08  0:54 ` Paul Clements [this message]
2005-06-08 17:15   ` Dan Stromberg
2005-06-08 17:51     ` Paul Clements
2005-06-08 18:00       ` Dan Stromberg
2005-06-08 18:23         ` Paul Clements
2005-06-08 18:28 ` Dan Stromberg

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=42A641CC.9040905@steeleye.com \
    --to=paul.clements@steeleye.com \
    --cc=linux-raid@vger.kernel.org \
    --cc=strombrg@dcs.nac.uci.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).