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 84F3110F9B for ; Fri, 6 Dec 2013 02:59:17 +0000 (UTC) Received: (qmail 99023 invoked by uid 500); 6 Dec 2013 02:59:14 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 98942 invoked by uid 500); 6 Dec 2013 02:59:14 -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 98934 invoked by uid 99); 6 Dec 2013 02:59:14 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 06 Dec 2013 02:59:14 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of ailinykh@gmail.com designates 209.85.215.45 as permitted sender) Received: from [209.85.215.45] (HELO mail-la0-f45.google.com) (209.85.215.45) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 06 Dec 2013 02:59:07 +0000 Received: by mail-la0-f45.google.com with SMTP id eh20so38137lab.4 for ; Thu, 05 Dec 2013 18:58:46 -0800 (PST) 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=83AFfixbscHC8PoN4B6G52ASvSh7HYRaOUPqGeOI53k=; b=G6qZ84X3mOOR4g+mA8AaH55y66+P9ud/J8ELt6djkvaibE1TXPptwDoyfrnQYU04Ui B+kzUhKmTSwyJlRptxaMcmhrzBl1myuJo9acfTUTzj4rb+Nhq3vUTLUJG0/LUYnvGC/7 4PnHZrmdik20h0h3ydGX2PvDHmPnCV02hg+K214IaCOgmMOrxakc3kFmsB/DLapuFUpb 5wwqhIZ7hEdg9nKnjf2BkNpJtaRn4UBFxJIxoMO4Gh7+LLysyl7794LGdrPRxT2JuZmC IVWdiBj0+vF4FenspwpR+6Cg9JtbswQi+KkzcKkrGVRUTFky6XZlAbXCpPcbJBTU6HPm BMwA== MIME-Version: 1.0 X-Received: by 10.152.238.34 with SMTP id vh2mr236317lac.50.1386298726333; Thu, 05 Dec 2013 18:58:46 -0800 (PST) Received: by 10.114.82.130 with HTTP; Thu, 5 Dec 2013 18:58:46 -0800 (PST) In-Reply-To: References: Date: Thu, 5 Dec 2013 18:58:46 -0800 Message-ID: Subject: Re: vnodes on aws From: Andrey Ilinykh To: user@cassandra.apache.org Content-Type: multipart/alternative; boundary=001a1134989c22c37704ecd4d30b X-Virus-Checked: Checked by ClamAV on apache.org --001a1134989c22c37704ecd4d30b Content-Type: text/plain; charset=ISO-8859-1 On Thu, Dec 5, 2013 at 3:31 PM, Jayadev Jayaraman wrote: > Availability zones are analogous to racks not data centres . EC2 regions > are equivalent to data centres. > Yes, this is what I meant. I guess my question is - is possible to put row in every rack using vnodes? Thank you, Andrey > On Dec 5, 2013 2:32 PM, "Andrey Ilinykh" wrote: > >> Hello everybody! >> We run cassandra 1.1 on ec2 instances. We use three availability zones, >> the replication factor is 3 also. NetworkTopologyStrategy guarantees each >> row is replicated in all availability zones. So, if we lost one zone quorum >> operations still work. We think about to upgrade to 1.2. Virtual nodes are >> the main reason. My understanding is - vnodes are distributed randomly, so >> their is no way to put every row into all availability zones. Am I right? >> What would be the best way to deploy vnodes across several data centers >> (availability zones)? >> >> >> Thank you, >> Andrey >> > --001a1134989c22c37704ecd4d30b Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable



On Thu, Dec 5, 2013 at 3:31 PM, Jayadev Jayaraman <jdisalive@gma= il.com> wrote:

Availability zones are analog= ous to racks not data centres . EC2 regions are equivalent to data centres.=

Yes, this is what I meant. I guess my question is - is po= ssible to put row in every rack using vnodes?

Than= k you,
=A0 =A0Andrey

=A0
On Dec 5= , 2013 2:32 PM, "Andrey Ilinykh" <ailinykh@gmail.com> wrote:
Hello everybody!
We run cassandra 1.1 on ec2 instances= . We use three availability zones, the replication factor is 3 also. Networ= kTopologyStrategy guarantees each row is replicated in all availability zon= es. So, if we lost one zone quorum operations still work. We think about to= upgrade to 1.2. Virtual nodes are the main reason. My understanding is - v= nodes are distributed randomly, so their is no way to put every row into al= l availability zones. =A0Am I right? What would be the best way to deploy v= nodes across several data centers (availability zones)?


Thank you,
=A0 Andrey=A0
=
--001a1134989c22c37704ecd4d30b--