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 9111418E26 for ; Wed, 9 Dec 2015 21:31:45 +0000 (UTC) Received: (qmail 73436 invoked by uid 500); 9 Dec 2015 21:31:40 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 73388 invoked by uid 500); 9 Dec 2015 21:31:40 -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 73376 invoked by uid 99); 9 Dec 2015 21:31:40 -0000 Received: from Unknown (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 09 Dec 2015 21:31:40 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id 8604A1A41A9 for ; Wed, 9 Dec 2015 21:31:39 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 2.898 X-Spam-Level: ** X-Spam-Status: No, score=2.898 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=3, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001] autolearn=disabled Authentication-Results: spamd2-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mx1-eu-west.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id KhGtuXuoQord for ; Wed, 9 Dec 2015 21:31:38 +0000 (UTC) Received: from mail-io0-f178.google.com (mail-io0-f178.google.com [209.85.223.178]) by mx1-eu-west.apache.org (ASF Mail Server at mx1-eu-west.apache.org) with ESMTPS id 552B920786 for ; Wed, 9 Dec 2015 21:31:38 +0000 (UTC) Received: by iofh3 with SMTP id h3so74326700iof.3 for ; Wed, 09 Dec 2015 13:26:24 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=tzB8j9Lw76q4Ebfa4qH4+rm/TznoQ1x9bJ9zHI/Ffko=; b=CNDe5FAntSfbW+0VDJi4h3VfjHdYBtbydNd49UvI3mjcW77NDBP6GL9FNAKFWxm9HX a9Zmg1+CEWiXK12Rh2iC0nNqYrCzYPM5JGbagn0am10Ksk5qDgDaT9k0k+efkspOZ7HA bd7NWkVOQR2sWyIcc0nq5kNt9QHttVN4D/ZaUw/+24SrXrVLisjx/R/mBNQGmIlEKnFj S9IBq9fJ2QoL5rkZiP1zMwOVvxI65vKuNWr8lQjR3DQrwEc7TM5pJaey4dIsA57ojfwZ qA5GVmrOXYHJa/6kTL6Ise68cIZdVUMzaNim8RgA0IbaFSe4lCf92BM1rah/+ehNZSkW Gp1A== MIME-Version: 1.0 X-Received: by 10.107.135.94 with SMTP id j91mr7830980iod.54.1449696384637; Wed, 09 Dec 2015 13:26:24 -0800 (PST) Received: by 10.64.13.198 with HTTP; Wed, 9 Dec 2015 13:26:24 -0800 (PST) Date: Wed, 9 Dec 2015 13:26:24 -0800 Message-ID: Subject: Switching to Vnodes From: cass savy To: user@cassandra.apache.org Content-Type: multipart/alternative; boundary=001a113ed44809dfb205267dbe06 --001a113ed44809dfb205267dbe06 Content-Type: text/plain; charset=UTF-8 We want to move our clusters to use Vnodes. I know the docs online say we have to create new DC with vnodes and move to new dC and decommission old one. We use DSE for our c* clusters.C* version is 2.0.14 1. Is there any other way to migrate existing nodes to vnodes? 2. What are the known issues with that approach? 3. We have few secondary indexes in the keyspace, will that cause any issues with moving to vnodes? 4. What are the issues encountered after moving to vnodes in PROD 5. anybody recommend Vnodes for Spark nodes. *Approach : Moving to new DC with vnodes enabled*: When I tested it for a keyspace which has secondary indexes, rebuilds on Vnode enabled Datacenter takes days and don't know when it completes or even if it will complete. I tried with 256,32,64 tokens per node but no luck. Please advise. --001a113ed44809dfb205267dbe06 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
We want to move our clusters to use Vnodes. I know the doc= s online say we have to create new DC with vnodes and move to new dC and de= commission old one. We use DSE for our c* clusters.C* version is 2.0.14
1. Is there any other way to migrate existing nodes to vnod= es?
2. What are the known issues with that approach?
3.= We have few secondary indexes in the keyspace, will that cause any issues = with moving to vnodes?

4. What are the issues enco= untered after moving to vnodes in PROD
5. anybody recommend Vnode= s for Spark nodes.

Approach : Moving to new DC = with vnodes enabled:
When I tested it for =C2=A0a =C2=A0keysp= ace which has secondary indexes, rebuilds on Vnode enabled Datacenter takes= days and don't know when it completes or even if it will complete. I t= ried with 256,32,64 tokens per node but no luck.=C2=A0

=
Please advise.

=C2=A0
--001a113ed44809dfb205267dbe06--