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 498631850F for ; Mon, 12 Oct 2015 10:17:15 +0000 (UTC) Received: (qmail 75635 invoked by uid 500); 12 Oct 2015 10:17:12 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 75596 invoked by uid 500); 12 Oct 2015 10:17:12 -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 75586 invoked by uid 99); 12 Oct 2015 10:17:12 -0000 Received: from Unknown (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 12 Oct 2015 10:17:12 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id E6346C26C6 for ; Mon, 12 Oct 2015 10:17:11 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 3 X-Spam-Level: *** X-Spam-Status: No, score=3 tagged_above=-999 required=6.31 tests=[HTML_MESSAGE=3, SPF_PASS=-0.001, WEIRD_QUOTING=0.001] autolearn=disabled Received: from mx1-us-west.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id BBCFfIiGHpl2 for ; Mon, 12 Oct 2015 10:17:10 +0000 (UTC) Received: from setentaytres29.nsprimario.com (setentaytres31.nsprimario.com [188.93.73.31]) by mx1-us-west.apache.org (ASF Mail Server at mx1-us-west.apache.org) with ESMTPS id C961420FD1 for ; Mon, 12 Oct 2015 10:17:09 +0000 (UTC) X-No-Relay: not in my network Received: from mail-wi0-f175.google.com (mail-wi0-f175.google.com [209.85.212.175]) by setentaytres29.nsprimario.com (Postfix) with ESMTPSA id 5904310A0F2B for ; Mon, 12 Oct 2015 12:17:00 +0200 (CEST) Received: by wijq8 with SMTP id q8so50392202wij.0 for ; Mon, 12 Oct 2015 03:16:59 -0700 (PDT) MIME-Version: 1.0 X-Received: by 10.180.12.241 with SMTP id b17mr14764860wic.55.1444645019971; Mon, 12 Oct 2015 03:16:59 -0700 (PDT) Received: by 10.27.85.31 with HTTP; Mon, 12 Oct 2015 03:16:59 -0700 (PDT) In-Reply-To: References: <156AA069D74CB042AA529A69006652531D6460D7@CO1PRD6102MB001.025d.mgd.msft.net> Date: Mon, 12 Oct 2015 11:16:59 +0100 Message-ID: Subject: Re: Is replication possible with already existing data? From: Carlos Alonso To: user@cassandra.apache.org Content-Type: multipart/alternative; boundary=001a11c366b63dfca00521e5a140 --001a11c366b63dfca00521e5a140 Content-Type: text/plain; charset=UTF-8 Yes Ajay, in your particular scenario, after all hints are delivered, both CAS11 and CAS12 will have the exact same data. Cheers! Carlos Alonso | Software Engineer | @calonso On 11 October 2015 at 05:21, Ajay Garg wrote: > Thanks a ton Anuja for the help !!! > > On Fri, Oct 9, 2015 at 12:38 PM, anuja jain wrote: > > Hi Ajay, > > > > > > On Fri, Oct 9, 2015 at 9:00 AM, Ajay Garg > wrote: > >> > > In this case, it will be the responsibility of APP1 to start connection > to > > CAS12. On the other hand if your APP1 is connecting to cassandra using > Java > > driver, you can add multiple contact points(CAS11 and CAS12 here) so > that if > > CAS11 is down it will directly connect to CAS12. > > Great .. Java-driver it will be :) > > > > > >> > > In such a case, CAS12 will store hints for the data to be stored on CAS11 > > (the tokens of which lies within the range of tokens CAS11 holds) and > > whenever CAS11 is up again, the hints will be transferred to it and the > data > > will be distributed evenly. > > > > Evenly? > > Should not the data be """EXACTLY""" equal after CAS11 comes back up > and the sync/transfer/whatever happens? > After all, before CAS11 went down, CAS11 and CAS12 were replicating all > data. > > > Once again, thanks for your help. > I will be even more grateful if you would help me clear the lingering > doubt to second point. > > > Thanks and Regards, > Ajay > --001a11c366b63dfca00521e5a140 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Yes Ajay, in your particular scenario, after all hints are= delivered, both CAS11 and CAS12 will have the exact same data.

Cheers!

Carlos Alonso | Software Engineer |=C2=A0@calonso

On 11 October 2015 at 05:21, Ajay Garg <ajaygargnsit@gmail.com> wrote:
Thanks a ton Anuja for the help !!!

On Fri, Oct 9, 2015 at 12:38 PM, anuja jain <anujajain4@gmail.com> wrote:
> Hi Ajay,
>
>
> On Fri, Oct 9, 2015 at 9:00 AM, Ajay Garg <ajaygargnsit@gmail.com> wrote:
>>
> In this case, it will be the responsibility of= APP1 to start connection to
> CAS12. On the other hand if your APP1 is connecting to cassandra using= Java
> driver, you can add multiple contact points(CAS11 and CAS12 here) so t= hat if
> CAS11 is down it will directly connect to CAS12.

Great .. Java-driver it will be :)




>>
> In such a case, CAS12 will store hints for the data to be stored on CA= S11
> (the tokens of which lies within the range of tokens CAS11 holds)=C2= =A0 and
> whenever CAS11 is up again, the hints will be transferred to it and th= e data
> will be distributed evenly.
>

Evenly?

Should not the data be """EXACTLY""" equal af= ter CAS11 comes back up
and the sync/transfer/whatever happens?
After all, before CAS11 went down, CAS11 and CAS12 were replicating all dat= a.


Once again, thanks for your help.
I will be even more grateful if you would help me clear the lingering
doubt to second point.


Thanks and Regards,
Ajay

--001a11c366b63dfca00521e5a140--