All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Kampe <mark.kampe@inktank.com>
To: James Horner <james.horner@precedent.co.uk>
Cc: ceph-devel@vger.kernel.org
Subject: Re: Client Location
Date: Tue, 09 Oct 2012 09:43:28 -0700	[thread overview]
Message-ID: <50745430.6090607@inktank.com> (raw)
In-Reply-To: <1467968321.440.1349788446710.JavaMail.root@corellia.pncl.co.uk>

I'm not a real engineer, so please forgive me if I misunderstand,
but can't you create a separate rule for each data center (choosing
first a local copy, and then remote copies), which should ensure
that the primary is always local.  Each data center would then
use a different pool, associated with the appropriate location-
sensitive rule.

Does this approach get you the desired locality preference?


  parent reply	other threads:[~2012-10-09 16:43 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1253073523.409.1349787553083.JavaMail.root@corellia.pncl.co.uk>
2012-10-09 13:14 ` Client Location James Horner
2012-10-09 13:30   ` Wido den Hollander
2012-10-09 13:33     ` james.horner
2012-10-09 16:43   ` Mark Kampe [this message]
2012-10-09 16:48     ` Gregory Farnum
2012-10-10  9:16       ` James Horner
2012-10-10 16:39         ` Sage Weil

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=50745430.6090607@inktank.com \
    --to=mark.kampe@inktank.com \
    --cc=ceph-devel@vger.kernel.org \
    --cc=james.horner@precedent.co.uk \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.