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 6163B10F8A for ; Tue, 5 Aug 2014 10:56:42 +0000 (UTC) Received: (qmail 2233 invoked by uid 500); 5 Aug 2014 10:56:39 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 2195 invoked by uid 500); 5 Aug 2014 10:56:39 -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 2184 invoked by uid 99); 5 Aug 2014 10:56:39 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 05 Aug 2014 10:56:39 +0000 X-ASF-Spam-Status: No, hits=2.2 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (nike.apache.org: local policy) Received: from [74.125.82.44] (HELO mail-wg0-f44.google.com) (74.125.82.44) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 05 Aug 2014 10:56:36 +0000 Received: by mail-wg0-f44.google.com with SMTP id m15so777806wgh.27 for ; Tue, 05 Aug 2014 03:56:08 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:content-type; bh=EPHiQeppPpQCBbzeAsobM7I9aKXI+QGB1+23JaCCA2g=; b=R81CqDQKVT/Vo+hYB3IOGADd0N3NH6EkDy04deJvQFlTKn2Q/5zJlhKPAQiHP3sc6B ELAntO1tvrKtOARUHVNhXWgnf+Q/rLEnz07RwofFMy2ULvirArbAH0Vo2HLSouVCzEnF HVUnkXf0AasJ2cE23SkMtFPgHrzjkO6Cyc0g98HG/nhRppfNVk4QxmdDu+qlNWH+IaLR WPUu7x8GdJO7m0qEiM8QFmE1BpF4LqYM1mRzw2AU5t+Z14ztQi1wtpUuFoJoK9eP/xBG 3fxXuEPerP6qbgZpQsoqN3RIuWIwQAwSo3BU9oJKPj/TDG04WlwPGknGH3VlOCnxzYyV tbjQ== X-Gm-Message-State: ALoCoQnfH2nQx6byw2pcoUs9vzHcPXlKLSP1XoOHVBFgSvDt1Y0Ucac3gZAEcGRaWJh/TTrw3iCk MIME-Version: 1.0 X-Received: by 10.194.19.165 with SMTP id g5mr4594207wje.65.1407236167370; Tue, 05 Aug 2014 03:56:07 -0700 (PDT) Received: by 10.194.55.135 with HTTP; Tue, 5 Aug 2014 03:56:07 -0700 (PDT) X-Originating-IP: [89.101.207.179] In-Reply-To: References: Date: Tue, 5 Aug 2014 11:56:07 +0100 Message-ID: Subject: Re: Make an existing cluster multi data-center compatible. From: Mark Reddy To: user@cassandra.apache.org Content-Type: multipart/alternative; boundary=047d7b4503aedf233804ffdfb30c X-Virus-Checked: Checked by ClamAV on apache.org --047d7b4503aedf233804ffdfb30c Content-Type: text/plain; charset=UTF-8 Yes, you must run a full repair for the reasons stated in the yaml file. Mark On Tue, Aug 5, 2014 at 11:52 AM, Rene Kochen wrote: > Hi all, > > I want to add a data-center to an existing single data-center cluster. > First I have to make the existing cluster multi data-center compatible. > > The existing cluster is a 12 node cluster with: > - Replication factor = 3 > - Placement strategy = SimpleStrategy > - Endpoint snitch = SimpleSnitch > > If I change the following: > - Placement strategy = NetworkTopologyStrategy > - Endpoint snitch = PropertyFileSnitch -> all 12 nodes in this file belong > to the same data-center and rack. > > Do I have to run full repairs after this change? Because the yaml file > states: IF YOU CHANGE THE SNITCH AFTER DATA IS INSERTED INTO THE CLUSTER, > YOU MUST RUN A FULL REPAIR, SINCE THE SNITCH AFFECTS WHERE REPLICAS ARE > PLACED. > > Thanks! > > Rene > > > --047d7b4503aedf233804ffdfb30c Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Yes, you must run a full repair for the reasons stated in = the yaml file.


Mark


On Tue, Aug 5, 2014 at = 11:52 AM, Rene Kochen <rene.kochen@schange.com> wrote:=
Hi all,

I want to ad= d a data-center to an existing single data-center cluster. First I have to = make the existing cluster multi data-center compatible.

The existing cluster is a 12 node cluster with:
- Replication factor =3D 3
- Placement strategy =3D SimpleStrategy
- = Endpoint snitch =3D SimpleSnitch

If I change the following:
- Pla= cement strategy =3D NetworkTopologyStrategy
- Endpoint snitch =3D Proper= tyFileSnitch -> all 12 nodes in this file belong to the same data-center= and rack.

Do I have to run full repairs after this change? Because the yaml file = states: IF YOU CHANGE THE SNITCH AFTER DATA IS INSERTED INTO THE CLUSTER, Y= OU MUST RUN A FULL REPAIR, SINCE THE SNITCH AFFECTS WHERE REPLICAS ARE PLAC= ED.

Thanks!

Rene
<= br>

--047d7b4503aedf233804ffdfb30c--