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 14ACA10F21 for ; Mon, 12 Aug 2013 21:10:36 +0000 (UTC) Received: (qmail 52335 invoked by uid 500); 12 Aug 2013 21:10:33 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 52307 invoked by uid 500); 12 Aug 2013 21:10:33 -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 52299 invoked by uid 99); 12 Aug 2013 21:10:33 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 12 Aug 2013 21:10:33 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW X-Spam-Check-By: apache.org Received-SPF: error (nike.apache.org: local policy) Received: from [209.85.220.49] (HELO mail-pa0-f49.google.com) (209.85.220.49) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 12 Aug 2013 21:10:27 +0000 Received: by mail-pa0-f49.google.com with SMTP id ld10so3468101pab.22 for ; Mon, 12 Aug 2013 14:09:46 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-gm-message-state:from:content-type:message-id:mime-version :subject:date:references:to:in-reply-to; bh=EjI5S7mv6UhD8sR7C3vpCaRj1MsqvtraqKUKz5oBGms=; b=byfJLw6PAji5d9/C3OhaFbLFbvyNNpLHnsior4k7COHqyXDqCRNSB8zKqq00xG7m04 ygjpwnty4MG3zzs2F/GfaBC9GGghYqvNH1q0m40v1pJifzPiwfJ3nthVtb6xjkNZj/Ik sreQCRMiCQewSFnOW2XbAavq3ULfpv+Rnwzh6KcNd7FsGGbJljhnPWH1BmGOgyl0FYU7 RsgHejIxYfpxHdm437hWp9sgGQR9knN5/VykiOI15T9ztzJtyy3qjmOkJVaHZHuRFBBu 8jMHmse7Q++VveG9bYbe0AxQmAj3eWwoYLkbO9Whn26bQ39cFqffJxYZOT0bCpKIBMgC B84g== X-Gm-Message-State: ALoCoQkPOoo/TMSWREgJRCa2mqTfS3HehOKhFr3RNprJ08vWxK9DeFHU9Q7IWzcmYSvFhGdYTglm X-Received: by 10.66.122.99 with SMTP id lr3mr28760pab.187.1376341786009; Mon, 12 Aug 2013 14:09:46 -0700 (PDT) Received: from [172.16.1.7] ([203.86.207.101]) by mx.google.com with ESMTPSA id z14sm39377154pbt.0.2013.08.12.14.09.44 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 12 Aug 2013 14:09:45 -0700 (PDT) From: Aaron Morton Content-Type: multipart/alternative; boundary="Apple-Mail=_57E4398B-A17A-448F-A128-5C8C250922AB" Message-Id: Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\)) Subject: Re: cassandra 1.2.5- virtual nodes (num_token) pros/cons? Date: Tue, 13 Aug 2013 09:09:43 +1200 References: To: user@cassandra.apache.org In-Reply-To: X-Mailer: Apple Mail (2.1508) X-Virus-Checked: Checked by ClamAV on apache.org --Apple-Mail=_57E4398B-A17A-448F-A128-5C8C250922AB Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=iso-8859-1 > Aaron - I read about the virtual nodes at = http://www.datastax.com/dev/blog/virtual-nodes-in-cassandra-1-2 Thanks, I did not see anything in there about making repair smoother / = faster.=20 Cheers A ----------------- Aaron Morton Cassandra Consultant New Zealand @aaronmorton http://www.thelastpickle.com On 10/08/2013, at 11:39 AM, rash aroskar = wrote: > Aaron - I read about the virtual nodes at = http://www.datastax.com/dev/blog/virtual-nodes-in-cassandra-1-2 >=20 >=20 >=20 >=20 >=20 >=20 >=20 >=20 > On Tue, Aug 6, 2013 at 4:49 AM, Richard Low = wrote: > On 6 August 2013 08:40, Aaron Morton wrote: >> The reason for me looking at virtual nodes is because of terrible = experiences we had with 0.8 repairs and as per documentation (an = logically) the virtual nodes seems like it will help repairs being = smoother. Is this true? > I've not thought too much about how they help repair run smoother, = what was the documentation you read ?=20 >=20 > There might be a slight improvement but I haven't observed any. The = difference might be that, because every node shares replicas with every = other (with high probability), a single repair operation does the same = work on the node it was called on, but the rest is spread out over the = cluster, rather than just the RF nodes either side of the repairing = node. This means the post-repair compaction work will take less time = and the length of time a node is loaded for during repair is less. >=20 > However, the other benefits of vnodes are likely to be much more = useful. >=20 > Richard. >=20 --Apple-Mail=_57E4398B-A17A-448F-A128-5C8C250922AB Content-Transfer-Encoding: 7bit Content-Type: text/html; charset=iso-8859-1
Aaron - I read about the virtual nodes at http://www.datastax.com/dev/blog/virtual-nodes-in-cassandra-1-2

Thanks, I did not see anything in there about making repair smoother / faster. 

Cheers
A
-----------------
Aaron Morton
Cassandra Consultant
New Zealand

@aaronmorton

On 10/08/2013, at 11:39 AM, rash aroskar <rashmi.aroskar@gmail.com> wrote:

Aaron - I read about the virtual nodes at http://www.datastax.com/dev/blog/virtual-nodes-in-cassandra-1-2








On Tue, Aug 6, 2013 at 4:49 AM, Richard Low <richard@wentnet.com> wrote:
On 6 August 2013 08:40, Aaron Morton <aaron@thelastpickle.com> wrote:
The reason for me looking at virtual nodes is because of terrible experiences we had with 0.8 repairs and as per documentation (an logically) the virtual nodes seems like it will help repairs being smoother. Is this true?
I've not thought too much about how they help repair run smoother, what was the documentation you read ? 

There might be a slight improvement but I haven't observed any.  The difference might be that, because every node shares replicas with every other (with high probability), a single repair operation does the same work on the node it was called on, but the rest is spread out over the cluster, rather than just the RF nodes either side of the repairing node.  This means the post-repair compaction work will take less time and the length of time a node is loaded for during repair is less.

However, the other benefits of vnodes are likely to be much more useful.

Richard.


--Apple-Mail=_57E4398B-A17A-448F-A128-5C8C250922AB--