All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jeff@garzik.org>
To: Pete Zaitcev <zaitcev@redhat.com>
Cc: Project Hail List <hail-devel@vger.kernel.org>
Subject: Re: [Patch] tabled: write objects to multiply chunks
Date: Tue, 29 Sep 2009 02:22:39 -0400	[thread overview]
Message-ID: <4AC1A7AF.1030802@garzik.org> (raw)
In-Reply-To: <20090925145919.12a7e697@redhat.com>

On 09/25/2009 04:59 PM, Pete Zaitcev wrote:
> This is a small, but self-contained step toward the data redundancy.
> The patch adds ability to write data to several Chunk servers.
> Along the way, it fixes things up so we use asynchronous writes.
>
> N.B. This patch changes the format of tabled's database in order to
> reflect that object IDs are global in the cell. This is done so the
> consistency checking and redundancy monitoring and recovery could
> be run without accessing the tabled's database. In orther words,
> it's a flag day, the database must be re-created.
>
> Signed-off-by: Pete Zaitcev<zaitcev@redhat.com>

applied



      reply	other threads:[~2009-09-29  6:22 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-25 20:59 [Patch] tabled: write objects to multiply chunks Pete Zaitcev
2009-09-29  6:22 ` Jeff Garzik [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=4AC1A7AF.1030802@garzik.org \
    --to=jeff@garzik.org \
    --cc=hail-devel@vger.kernel.org \
    --cc=zaitcev@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 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.