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: Wed, 08 Jun 2005 14:23:35 -0400	[thread overview]
Message-ID: <42A737A7.4080806@steeleye.com> (raw)
In-Reply-To: <1118253658.15459.158.camel@seki.nac.uci.edu>

Dan Stromberg wrote:

> Is the difficulty mostly stemming from keeping stateful sessions and
> content consistent across replica servers?

Yes, that's it, more or less.

--
Paul

  reply	other threads:[~2005-06-08 18:23 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
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 [this message]
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=42A737A7.4080806@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).