From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jeff Garzik Subject: Re: [PATCH v1] CLD replication (WIP) Date: Fri, 31 Jul 2009 14:52:59 -0400 Message-ID: <4A733D8B.9010101@garzik.org> References: <20090731104031.GA21249@havoc.gtf.org> <4A733A26.2080801@garzik.org> Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <4A733A26.2080801@garzik.org> Sender: hail-devel-owner@vger.kernel.org List-ID: Content-Type: text/plain; charset="us-ascii"; format="flowed" To: Sage Weil Cc: hail-devel@vger.kernel.org Jeff Garzik wrote: > Sage Weil wrote: >> Hi Jeff, >> >> Do you still plan to replace bdb (and it's replication) with a >> something based on paxos? I'm considering replacing the Ceph monitors >> (which currently implement paxos, but in a very ceph-specific way) >> with cld if it can meet the basic requirements. >> >> What I'd kind of like to see is a clean implementation of a paxos >> library--one that leaves out message transport and storage--to build a >> replicated write-ahead log. And then a separate library for handling >> the database/namespace served up by cld (be it regular files, bdb, >> whatever) that leaves replication up to paxos. It looks like Google >> ended up doing something similar with Chubby (see >> http://labs.google.com/papers/paxos_made_live.html). >> >> Does this sound like the direction you guys are heading in? > > You mean something like http://linux.yyz.us/misc/paxreg.c ? :) Oh, and the paper related to this is "The Paxos Register", http://www.cs.utexas.edu/~harry/papers/Li07Paxos.pdf Jeff