Return-Path: 
 <user-return-41011-apmail-cassandra-user-archive=cassandra.apache.org@cassandra.apache.org>
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 1A09110A7C
	for <apmail-cassandra-user-archive@www.apache.org>;
 Wed,  4 Jun 2014 21:03:14 +0000 (UTC)
Received: (qmail 1506 invoked by uid 500); 4 Jun 2014 21:03:11 -0000
Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org
Received: (qmail 1465 invoked by uid 500); 4 Jun 2014 21:03:11 -0000
Mailing-List: contact user-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:user-help@cassandra.apache.org>
List-Unsubscribe: <mailto:user-unsubscribe@cassandra.apache.org>
List-Post: <mailto:user@cassandra.apache.org>
List-Id: <user.cassandra.apache.org>
Reply-To: user@cassandra.apache.org
Delivered-To: mailing list user@cassandra.apache.org
Received: (qmail 1457 invoked by uid 99); 4 Jun 2014 21:03:11 -0000
Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 04 Jun 2014 21:03:11 +0000
X-ASF-Spam-Status: No, hits=2.2 required=5.0
	tests=HTML_MESSAGE,RCVD_IN_DNSWL_NONE,SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (athena.apache.org: domain of pipelines@gmail.com
 designates 209.85.192.42 as permitted sender)
Received: from [209.85.192.42] (HELO mail-qg0-f42.google.com) (209.85.192.42)
    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 04 Jun 2014 21:03:06 +0000
Received: by mail-qg0-f42.google.com with SMTP id q107so129332qgd.15
        for <user@cassandra.apache.org>; Wed, 04 Jun 2014 14:02:46 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type;
        bh=iXO0FSv/gUUm60F/oG9likSoPhfOTrhVS4jqk4o7rTo=;
        b=gLDS6XlxNKZ2uNxKFJHoazNVx59uBGVmgQCs14PmcbRq3By6qHW3OYWbvojYDf41TW
         /IgyvcpsMk2gl459HAuPIY4q/t7XGTPNTJykdh0/7qPMbOL4mWb3YpdlI++1deS/Zqg2
         3zzX7/K4K3i1swfNpbIoev2dnuqeK56NzMjpNUf+V5xbTTNZUg+RcOb4DfI9mVDNV1OV
         bQL63kY7Mosq04mAsr5gTlr50SviKdGX2fAjtxLLjdrDz7I+ojSACJvkVMqOvC0S7Dr3
         WFYOVq+k8TJPVdd8BiB16fOXcQM/lFXxwwbryapQl7/DIHI0K/qVBoa7aJRcYsuugZRL
         /9cQ==
MIME-Version: 1.0
X-Received: by 10.140.87.5 with SMTP id q5mr73487634qgd.43.1401915766207; Wed,
 04 Jun 2014 14:02:46 -0700 (PDT)
Received: by 10.224.107.3 with HTTP; Wed, 4 Jun 2014 14:02:46 -0700 (PDT)
In-Reply-To: 
 <CAEDUwd2=qx-dR2khhMkJr7V6r6sJnuSnZVbULRs+3-i3cXAR9A@mail.gmail.com>
References: 
 <CAAQKod16tzgNO8npJ6-m7o+ammFb+VD7+PR=xYtpH-2jxx81sQ@mail.gmail.com>
	<CAEDUwd2=qx-dR2khhMkJr7V6r6sJnuSnZVbULRs+3-i3cXAR9A@mail.gmail.com>
Date: Wed, 4 Jun 2014 15:02:46 -0600
Message-ID: 
 <CAAQKod1C8XK5nF42ztCipcvHr4sPtYr5Up5rS1uheL5Z7FQtnA@mail.gmail.com>
Subject: Re: Snapshot the data with 3 node and replicationfactor=3
From: ng <pipelines@gmail.com>
To: "user@cassandra.apache.org" <user@cassandra.apache.org>
Content-Type: multipart/alternative; boundary=001a113ab2ec40939504fb08f30c
X-Virus-Checked: Checked by ClamAV on apache.org

--001a113ab2ec40939504fb08f30c
Content-Type: text/plain; charset=UTF-8

I am not worried about eventually consistent data. I just wanted to get
rough data in close proximate.
ng


On Wed, Jun 4, 2014 at 2:49 PM, Robert Coli <rcoli@eventbrite.com> wrote:

> On Wed, Jun 4, 2014 at 1:26 PM, ng <pipelines@gmail.com> wrote:
>
>> Is there any reason you would like to take snapshot of column family on
>> each node when cluster consists of 3 nodes with keyspace on replication
>> factor =3?
>>
>
> Unless all read/write occurs with CL.ALL (which is an availability
> problem), there is a nonzero chance of any given write not being on any
> given node at any given time.
>
> =Rob
>
>

--001a113ab2ec40939504fb08f30c
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>I am not worried about eventually consistent data. I =
just wanted to get rough data in close proximate.<br>ng</div></div><div cla=
ss=3D"gmail_extra"><br><br><div class=3D"gmail_quote">On Wed, Jun 4, 2014 a=
t 2:49 PM, Robert Coli <span dir=3D"ltr">&lt;<a href=3D"mailto:rcoli@eventb=
rite.com" target=3D"_blank">rcoli@eventbrite.com</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div dir=3D"ltr"><div class=3D"gmail_extra">=
<div class=3D"gmail_quote"><div>On Wed, Jun 4, 2014 at 1:26 PM, ng <span di=
r=3D"ltr">&lt;<a href=3D"mailto:pipelines@gmail.com" target=3D"_blank">pipe=
lines@gmail.com</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;padding=
-left:1ex;border-left-color:rgb(204,204,204);border-left-width:1px;border-l=
eft-style:solid">
<div dir=3D"ltr"><div>Is there any reason you would like to take snapshot o=
f column family on each node when cluster consists of 3 nodes with keyspace=
 on replication factor =3D3?<br></div></div></blockquote><div><br></div></d=
iv>
<div>
Unless all read/write occurs with CL.ALL (which is an availability problem)=
, there is a nonzero chance of any given write not being on any given node =
at any given time.</div><div><br></div><div>=3DRob</div><div><br></div></di=
v>

</div></div>
</blockquote></div><br></div>

--001a113ab2ec40939504fb08f30c--