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 B861010250 for ; Tue, 8 Apr 2014 08:30:51 +0000 (UTC) Received: (qmail 6572 invoked by uid 500); 8 Apr 2014 08:30:47 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 6246 invoked by uid 500); 8 Apr 2014 08:30:46 -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 6228 invoked by uid 99); 8 Apr 2014 08:30:44 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 08 Apr 2014 08:30:44 +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 veeseekay@gmail.com designates 209.85.214.169 as permitted sender) Received: from [209.85.214.169] (HELO mail-ob0-f169.google.com) (209.85.214.169) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 08 Apr 2014 08:30:39 +0000 Received: by mail-ob0-f169.google.com with SMTP id va2so647793obc.28 for ; Tue, 08 Apr 2014 01:30:16 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:from:date:message-id:subject:to:content-type; bh=wI726c3Q4fzx+1QLX3vgNcFOMLDWOdviOyuPAqSNmB8=; b=TrDltb6gWCybDBa6rmiArWXEpt5IMTdzS9ylScbpR8jToaRMjBKmSSNZto0dCE9G+d H9FQ+6s/OKLTPdE/rzg6VpzgzoJFG91k/trnRNQ0Nxt42G76UNOCwaz0yVNQCTloq9Eo Ain3QLBayKEam5BtcOkmmjDVpmcR+LWfM1Vs2jGdXz4RpRHZgZRpQxQKXT1ZrkiLU4Dc zkokGCEmO2+Qn+cMzZqEuTCwpQ1xPX/dMrMZQ9wrrN0z+XjIQu6em81SwiRVJfHur5VF NxSeQr1GJHuDhp/YIUIdDbfDcgyPaIP45k6FH4FFjWH5oaSb1Vu1CaRuJAbW1KkqP4Pg 88LA== X-Received: by 10.182.81.197 with SMTP id c5mr2203542oby.40.1396945816723; Tue, 08 Apr 2014 01:30:16 -0700 (PDT) MIME-Version: 1.0 Received: by 10.76.34.71 with HTTP; Tue, 8 Apr 2014 01:29:56 -0700 (PDT) From: vck Date: Tue, 8 Apr 2014 13:59:56 +0530 Message-ID: Subject: Vnodes and replication To: user@cassandra.apache.org Content-Type: multipart/alternative; boundary=047d7b2e4d582d27fa04f683cbdc X-Virus-Checked: Checked by ClamAV on apache.org --047d7b2e4d582d27fa04f683cbdc Content-Type: text/plain; charset=ISO-8859-1 After reading through the vnodes and partitioning described in the datastax documentation, I am still confused about how rows are partitioned/replicated. With vnodes, I know that each Node on the ring now supports many token ranges per Node. However I am still not very clear on how the replication is carried out. If I have 4 Nodes A, B, C, D and their ranges are below. A - [1,2,3,4] B - [5,6,7,8] C - [9,10,11,12] D - [13,14,15,16] After a shuffle, lets assume the Nodes are shuffled like this. A - [1,5,13,9] B - [2,6,14,10] C - [3,7,15,11] D - [4,8,16,12] now if I use a simple replication strategy and RF=3, the first replica rowkey gets placed on node determined by the partitioner. Prior to vnode, if my rowkey hash is 2, it gets placed on Nodes A, B, C. With the above vnode setup, if my rowkey hash is 2, does it get placed in B, C, D ? cheers! --047d7b2e4d582d27fa04f683cbdc Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable

After reading through the vnodes and partitioning described in the datastax= documentation, I am still confused about how rows are partitioned/replicat= ed.

With vnodes, I know that each Node on the ring now supports many token rang= es per Node. However I am still not very clear on how the replication is ca= rried out.

If I have 4 Nodes A, B, C, D and their ranges are below.


A - [1,2,3,4]
B - [5,6,7,8]
C - [9,10,11,12]
D - [13,14,15,16] =20

After a shuffle, lets assume the Nodes are shuffled like this.


A - [1,5,13,9]
B - [2,6,14,10]
C - [3,7,15,11]
D - [4,8,16,12]

now if I use a simple replication strategy and=A0RF=3D3, the first replica rowkey gets placed on node determined by the parti= tioner.

Prior to vnode, if my rowkey hash is 2, it gets placed on Nodes A, B, C. Wi= th the above vnode setup, if my rowkey hash is 2, does it get placed in B, = C, D ?

cheers!

--047d7b2e4d582d27fa04f683cbdc--