Return-Path: X-Original-To: apmail-cassandra-user-archive@www.apache.org Delivered-To: apmail-cassandra-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 055E2DA0C for ; Tue, 14 Aug 2012 20:58:11 +0000 (UTC) Received: (qmail 55394 invoked by uid 500); 14 Aug 2012 20:58:08 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 55368 invoked by uid 500); 14 Aug 2012 20:58:08 -0000 Mailing-List: contact user-help@cassandra.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@cassandra.apache.org Delivered-To: mailing list user@cassandra.apache.org Received: (qmail 55359 invoked by uid 99); 14 Aug 2012 20:58:08 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 14 Aug 2012 20:58:08 +0000 X-ASF-Spam-Status: No, hits=2.2 required=5.0 tests=FSL_RCVD_USER,HTML_MESSAGE,RCVD_IN_DNSWL_NONE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: local policy) Received: from [208.113.200.5] (HELO homiemail-a42.g.dreamhost.com) (208.113.200.5) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 14 Aug 2012 20:58:01 +0000 Received: from homiemail-a42.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a42.g.dreamhost.com (Postfix) with ESMTP id 516AF68C05D for ; Tue, 14 Aug 2012 13:57:40 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=thelastpickle.com; h=from :content-type:message-id:mime-version:subject:date:references:to :in-reply-to; s=thelastpickle.com; bh=1pc8mKkKeEHKVC39zh4p955+5R E=; b=31013f8TcHLTJzln1I8/FDPJFLSlgmPH25a5a1CBjjzG/DnfURaaFBLGqF +ZKpfgqK529QOLQeG+NLcwp/NEFNFwdnv2tB2nwpCaewI6y2PGPOJ7BDBYvn9dRi MnYqK6ffqvJlpZyZ3r+3lGQV9QhePav6ZaOIVgwoD7yc5uJ3c= Received: from [192.168.2.77] (unknown [116.90.132.105]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: aaron@thelastpickle.com) by homiemail-a42.g.dreamhost.com (Postfix) with ESMTPSA id CDC9968C058 for ; Tue, 14 Aug 2012 13:57:39 -0700 (PDT) From: aaron morton Content-Type: multipart/alternative; boundary="Apple-Mail=_13C7F141-9307-4006-8EDD-C2336B2E0E8D" Message-Id: Mime-Version: 1.0 (Mac OS X Mail 6.0 \(1485\)) Subject: Re: incremental backup and Priam? Date: Wed, 15 Aug 2012 08:57:36 +1200 References: To: user@cassandra.apache.org In-Reply-To: X-Mailer: Apple Mail (2.1485) --Apple-Mail=_13C7F141-9307-4006-8EDD-C2336B2E0E8D Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=iso-8859-1 The Priam code is looking for the //backups = directory created by cassandra during incremental backups. If it finds = it the files are uploaded to S3.=20 It's taking the built in incremental backups off node. (AFAIK) Cheers ----------------- Aaron Morton Freelance Developer @aaronmorton http://www.thelastpickle.com On 15/08/2012, at 8:16 AM, Yang wrote: > in the initial incremental backup implementation,=20 > the hardlinking to the backup dir was in the CFS.addSSTable() code, = so it's part of the Cassandra code. >=20 > I looked at Priam, = https://github.com/Netflix/Priam/blob/master/priam/src/main/java/com/netfl= ix/priam/backup/IncrementalBackup.java >=20 > this code pretty much does the same thing as the original addSSTable() = incremental backup . > so the Priam backup code operates outside of Cassandra write path? > any insight into why this approach was chosen instead of using the = incremental backup provided by Cassandra? >=20 > thanks > Yang --Apple-Mail=_13C7F141-9307-4006-8EDD-C2336B2E0E8D Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=iso-8859-1 The = Priam code is looking for the = <keyspace>/<columnfamily>/backups directory created by = cassandra during incremental backups. If it finds it the files are = uploaded to S3. 

It's taking the built in = incremental backups off node. = (AFAIK)

Cheers

http://www.thelastpickle.com

On 15/08/2012, at 8:16 AM, Yang <teddyyyy123@gmail.com> = wrote:

in the initial incremental backup = implementation, 
the hardlinking to the backup dir was in the = CFS.addSSTable()  code, so it's part of the Cassandra = code.


this code pretty much does the same thing as the = original addSSTable() incremental backup .
so the Priam backup = code operates outside of Cassandra write path?
any insight = into why this approach was chosen instead of using the incremental = backup provided by Cassandra?

thanks
Yang

= --Apple-Mail=_13C7F141-9307-4006-8EDD-C2336B2E0E8D--