Mailing-List: contact cassandra-user-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: cassandra-user@incubator.apache.org
Received-SPF: pass (nike.apache.org: domain of jbellis@gmail.com designates
 209.85.219.205 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type:content-transfer-encoding;
        b=g9/mgZimWTAOcLfGVro0zqOUNvfOZb3Oe7oGVtRdQmsTsduRI0lg9iPamMDUtm1QDF
         301SDkgIedf2TF2QDPs7I8kj0BMUaKRKXYzGnANEnCY9uexKxi2hOWsKZnJVGdcBWRaB
         5Gc5mWvmS7MzRb7t2dWMUxf71EKMGfo2jfwhk=
MIME-Version: 1.0
In-Reply-To: <20091005161048.GA45561@alumni.caltech.edu>
References: <f05b8c590910042252q4b026d1ape3fa13a3c243f1d@mail.gmail.com>
	 <e06563880910050522n2852c1d6pa765a53abe438c3b@mail.gmail.com>
	 <c715e640910050605g180df53cue78ace13105b30c3@mail.gmail.com>
	 <e06563880910050609h1a9f05d3s7dce13e2218b77e5@mail.gmail.com>
	 <20091005161048.GA45561@alumni.caltech.edu>
Date: Mon, 5 Oct 2009 11:17:48 -0500
Message-ID: <e06563880910050917u58f18524r39f040128ec79e45@mail.gmail.com>
Subject: Re: backing up data from cassandra
From: Jonathan Ellis <jbellis@gmail.com>
To: cassandra-user@incubator.apache.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

On Mon, Oct 5, 2009 at 11:10 AM, Anthony Molinaro
<anthonym@alumni.caltech.edu> wrote:
> I assume the server also needs to be stopped while your are swapping
> files, but what about if you have a cluster of several servers and
> need to restore. =A0Is the process to shutdown all the servers, move
> the files and restart?=A0Or can you you do it one at a time. =A0(I assume
> one at a time might mean a lot of read-repair work happening, so not
> a good idea).

Right, you could end up with newer data mixed in with your backed up
version which is probably not what you want.

> Also, is it best to flush_binary (which I think flushes in memory
> tables to disk), and compact prior to snapshotting?

flush_binary only acts on the binary memtables.  I wrote earlier:

>> note that the 0.4 branch, which will become 0.4.1, automatically
>> flushes each columnfamily when you ask for a snapshot of the table, so
>> you don't have to do that manually anymore.

Compaction isn't necessary and would slow down snapshotting considerably.

-Jonathan