Return-Path: Delivered-To: apmail-incubator-cassandra-dev-archive@minotaur.apache.org Received: (qmail 92980 invoked from network); 25 Feb 2010 15:20:29 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 25 Feb 2010 15:20:29 -0000 Received: (qmail 75184 invoked by uid 500); 25 Feb 2010 15:20:28 -0000 Delivered-To: apmail-incubator-cassandra-dev-archive@incubator.apache.org Received: (qmail 75168 invoked by uid 500); 25 Feb 2010 15:20:28 -0000 Mailing-List: contact cassandra-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: cassandra-dev@incubator.apache.org Delivered-To: mailing list cassandra-dev@incubator.apache.org Received: (qmail 75160 invoked by uid 99); 25 Feb 2010 15:20:28 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 25 Feb 2010 15:20:28 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of jbellis@gmail.com designates 74.125.82.47 as permitted sender) Received: from [74.125.82.47] (HELO mail-ww0-f47.google.com) (74.125.82.47) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 25 Feb 2010 15:20:20 +0000 Received: by wwb22 with SMTP id 22so1879934wwb.6 for ; Thu, 25 Feb 2010 07:20:00 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :from:date:message-id:subject:to:content-type :content-transfer-encoding; bh=9fN70Rnm4r2NjV0Jya8ADEb+s5fM5rc62pL7pG7mLTo=; b=Imz7XLmu+nvA8nAuMo+NL6/sTkIyD2iPfsFfSrS866xkgqAX9G4NPxcgj/yC4FtU4y uMfsGj6/v3s6BFtQ+f0V3G6tNJyZdIIvzimeVvhT027Hl7pMZCK4lISGFw273lB3x2Gr M4Eav+CcAv2i3entiQ6PinDk+a10YeR3xZ6dk= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type:content-transfer-encoding; b=fzBmf69Ul4UOKlVFp9N6++41OaCDHoOK4kvWhZtFIDjRmATkPXtKtjAxwgczLr37yD wIeK+GLvjqir56Zj6/ga/OVHKP+Na4KaDxc4ox6skQlU742ZZpsj0myY3dQ9Pfgjw+lf bvJHZ9Iq/qY6EiiuzOLDd8ULUg1+F+sazpNoA= MIME-Version: 1.0 Received: by 10.216.91.82 with SMTP id g60mr780209wef.98.1267111200115; Thu, 25 Feb 2010 07:20:00 -0800 (PST) In-Reply-To: <87sk8puyym.fsf@lifelogs.com> References: <87tyt7y63f.fsf@lifelogs.com> <87pr3vy3p2.fsf@lifelogs.com> <87tyt72z3p.fsf@lifelogs.com> <87iq9lwhpo.fsf_-_@lifelogs.com> <87sk8puyym.fsf@lifelogs.com> From: Jonathan Ellis Date: Thu, 25 Feb 2010 09:19:40 -0600 Message-ID: Subject: Re: consistent backups To: cassandra-dev@incubator.apache.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Virus-Checked: Checked by ClamAV on apache.org Go ahead. 2010/2/25 Ted Zlatanov : > On Thu, 25 Feb 2010 08:22:38 -0600 Jonathan Ellis wro= te: > > JE> 2010/2/25 Ted Zlatanov : >>> I want a consistent backup. > > JE> You can get an "eventually consistent backup" by flushing all nodes > JE> and snapshotting; no individual node's backup is guaranteed to be > JE> consistent but if you restore from that snapshot then clients will ge= t > JE> eventually consistent behavior as usual. > > JE> Other than that there is no such thing as a "consistent view of the > JE> data" in the strict sense, except in the trivial case of writes with > JE> CL.ALL. > > That makes perfect sense, thanks for explaining. =A0Can the explanation b= e > part of the http://wiki.apache.org/cassandra/Operations section on > backups? =A0I'll submit the edit if you want. > > Thanks > Ted > >