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 A40B711F4C for ; Fri, 4 Jul 2014 14:45:57 +0000 (UTC) Received: (qmail 44387 invoked by uid 500); 4 Jul 2014 14:45:55 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 44345 invoked by uid 500); 4 Jul 2014 14:45:55 -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 44330 invoked by uid 99); 4 Jul 2014 14:45:55 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 04 Jul 2014 14:45:55 +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 [209.85.212.174] (HELO mail-wi0-f174.google.com) (209.85.212.174) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 04 Jul 2014 14:45:51 +0000 Received: by mail-wi0-f174.google.com with SMTP id bs8so13038131wib.1 for ; Fri, 04 Jul 2014 07:45:24 -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=V3YGTSZzDcpzuqrKhAfNmd3CuMAFgId7uyqopqDveME=; b=Lfy6GVud7EOt68ANcs5/XFfNdd/3RKZdcl6k8fVX3aqwB6bDG+Af00DnGtpSldJ8Zu eJzoCIXypqWR9kiGEaW0enqBD4WbAH063esdb4SeMN1QogJ14kzNT5DS/DlDPqHZt5NO mDoPhiVh+X1CQtaPCEwtOlBlZeFBNi6yCHhNFq43dVgI5VLOwTzgdub1Xcu4jWtEAOpT UPOqrMoSRw22HfsenYi5/iVomRYVCRcXFP7S8678yaf/xX+bLARIEZ4rFZhgZqGAoYeI 1YWpYGyz3f4IsdbI16P0NlOt/uyU67ODTwnGOhzVlyrNpFA7nxAxUgV8+NFyU8rmkS4v 6M5Q== X-Gm-Message-State: ALoCoQmF3ky5EdkqqkDK7RF75D9quqcFzMSjyUnQusZAHLLJ6vvXcQdHu+yGHWnB5EmYWXaBUgQr MIME-Version: 1.0 X-Received: by 10.180.221.162 with SMTP id qf2mr17945474wic.75.1404484808762; Fri, 04 Jul 2014 07:40:08 -0700 (PDT) Received: by 10.194.234.41 with HTTP; Fri, 4 Jul 2014 07:40:08 -0700 (PDT) X-Originating-IP: [193.1.209.101] In-Reply-To: References: Date: Fri, 4 Jul 2014 15:40:08 +0100 Message-ID: Subject: Re: Disable vnode From: Mark Reddy To: user@cassandra.apache.org Content-Type: multipart/alternative; boundary=001a1135f2001eca7d04fd5f1ac4 X-Virus-Checked: Checked by ClamAV on apache.org --001a1135f2001eca7d04fd5f1ac4 Content-Type: text/plain; charset=UTF-8 Hi Rameez, If you run a rebuild on an already populated cluster it will simply stream the data again and you will have a duplicate data set. What you need to do is stop all the nodes in the new DC and clear out the data directory. Then comment out num_tokens and populate the initial token with the correct token as calculated by the token generator, packaged with cassandra "/tools/bin/token-generator" Once that is complete follow the steps in the link I provided and that should get your new DC running on non-vnodes. On Fri, Jul 4, 2014 at 3:12 PM, Rameez Thonnakkal wrote: > i did a nodetool rebuild on one of the nodes. > > Datacenter: DC1 > ================ > Status=Up/Down > |/ State=Normal/Leaving/Joining/Moving > -- Address Load Tokens Owns Host > ID Rack > *UN 10.123.75.51 10.54 GB 256 16.0% > d2f980c1-cf82-4659-95ce-ffa3e50ed7c1 RAC1* > UN 10.123.75.53 5.18 GB 256 16.5% > bab7739d-c424-42ef-a8f6-2ba82fcdd0b9 RAC1 > UN 10.123.75.52 5.51 GB 256 18.3% > 70469a76-939b-4b8c-9512-33aedec6fd3e RAC1 > Datacenter: DC2 > ================ > Status=Up/Down > |/ State=Normal/Leaving/Joining/Moving > -- Address Load Tokens Owns Host > ID Rack > UN 10.123.75.51 5.3 GB 256 16.1% > 106d5001-2d44-4d81-8af8-5cf841a1575e RAC1 > UN 10.123.75.52 5.34 GB 256 16.2% > c4333d90-476a-4b44-bc23-5fca7ba6a2e7 RAC1 > UN 10.123.75.53 5.11 GB 256 16.8% > 8154288e-a0fb-45f8-b3fb-6c3d645ba8f3 RAC1 > > In that node the Load has increased from around 5GB to 10GB. > But the tokens remains same (256). My expectation was that it would come > down to 1. > > i will continue to rebuild the remaining nodes. But not sure whether this > is helping. > > > > On Fri, Jul 4, 2014 at 7:28 PM, Rameez Thonnakkal > wrote: > >> Thanks Mark. >> the procedure you shared is useful. I think I have missed the nodetool >> rebuild command. >> I am trying it out in a non-prod environment. >> >> The num_tokens is set to 1 and initial_token is set to different values >> (mine is a 6 node cluster with 3 in each datacenter). >> Tried a rolling restart of the cluster. That didn't help. >> Tried a cold restart of the cluster. That also didn't work. >> >> I will try the nodetool rebuild and see whether any change. >> >> Thanks, >> rameez >> >> >> >> On Fri, Jul 4, 2014 at 7:19 PM, Mark Reddy >> wrote: >> >>> Hi Rameez, >>> >>> I have never done a migration from vnodes to non-vnodes however I would >>> imagine that the procedure would be the same as its counterpart. As always >>> testing in dev should be done first. >>> >>> To move from vnodes to non-vodes I would add a new datacenter to the >>> cluster with vnodes disabled and rebuild from your vnode cluster. >>> >>> You can find some more details about adding a data center to your >>> cluster here: >>> http://datastax.com/documentation/cassandra/2.0/cassandra/operations/ops_add_dc_to_cluster_t.html?scroll=task_ds_hmp_54q_gk__task_ds_hmp_54q_gk_unique_1 >>> >>> >>> >>> Mark >>> >>> >>> >>> On Fri, Jul 4, 2014 at 2:43 PM, Rameez Thonnakkal >>> wrote: >>> >>>> hello Team, >>>> >>>> I am looking for standard operating procedure to disable vnode in a >>>> production cluster. >>>> This is to enable solr which doesn't work with a cassandra cluster >>>> having vnode enabled. >>>> >>>> Any suggestions/ >>>> >>>> Thanks, >>>> Rameez >>>> >>>> >>> >> > --001a1135f2001eca7d04fd5f1ac4 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hi Rameez,

If you run a rebuild on an already populated cluster it wil= l simply stream the data again and you will have a duplicate data set.

Wha= t you need to do is stop all the nodes in the new DC and clear out the data= directory. Then comment out num_tokens and populate the initial token with= the correct token as calculated by the token generator, packaged with cass= andra "/tools/bin/token-genera= tor"

Once that is complete follow the steps in the link I prov= ided and that should get your new DC running on non-vnodes.


On Fri, Jul 4= , 2014 at 3:12 PM, Rameez Thonnakkal <ssrameez@gmail.com> w= rote:
i did a node= tool rebuild on one of the nodes.

Datacenter: DC1
=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
Status=3DUp/Down
|/ State=3DNormal/Leaving/Joining/Moving
--=C2=A0 Ad= dress=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 Load=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0 Tokens=C2=A0 Owns=C2=A0=C2=A0 Host ID=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0= =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0 Rack
UN=C2=A0 10.123.75.51=C2=A0 10.54 GB=C2=A0=C2=A0 256=C2=A0=C2=A0=C2=A0= =C2=A0 16.0%=C2=A0 d2f980c1-cf82-4659-95ce-ffa3e50ed7c1=C2=A0 RAC1
U= N=C2=A0 10.123.75.53=C2=A0 5.18 GB=C2=A0=C2=A0=C2=A0 256=C2=A0=C2=A0=C2=A0= =C2=A0 16.5%=C2=A0 bab7739d-c424-42ef-a8f6-2ba82fcdd0b9=C2=A0 RAC1
UN=C2= =A0 10.123.75.52=C2=A0 5.51 GB=C2=A0=C2=A0=C2=A0 256=C2=A0=C2=A0=C2=A0=C2= =A0 18.3%=C2=A0 70469a76-939b-4b8c-9512-33aedec6fd3e=C2=A0 RAC1
Datacenter: DC2
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
Stat= us=3DUp/Down
|/ State=3DNormal/Leaving/Joining/Moving
--=C2=A0 Addres= s=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 Load=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0 Tokens=C2=A0 Owns=C2=A0=C2=A0 Host ID=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0= =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 Ra= ck
UN=C2=A0 10.123.75.51=C2=A0 5.3 GB=C2=A0=C2=A0=C2=A0=C2=A0 256=C2=A0= =C2=A0=C2=A0=C2=A0 16.1%=C2=A0 106d5001-2d44-4d81-8af8-5cf841a1575e=C2=A0 R= AC1
UN=C2=A0 10.123.75.52=C2=A0 5.34 GB=C2=A0=C2=A0=C2=A0 256=C2=A0=C2=A0=C2=A0= =C2=A0 16.2%=C2=A0 c4333d90-476a-4b44-bc23-5fca7ba6a2e7=C2=A0 RAC1
UN=C2= =A0 10.123.75.53=C2=A0 5.11 GB=C2=A0=C2=A0=C2=A0 256=C2=A0=C2=A0=C2=A0=C2= =A0 16.8%=C2=A0 8154288e-a0fb-45f8-b3fb-6c3d645ba8f3=C2=A0 RAC1

In that node the Load has increased from around 5GB to 10GB.
But the tokens remains same (256). My expectation was that it would c= ome down to 1.

i will continue to rebuild the remaining nodes= .=C2=A0 But not sure whether this is helping.



On Fri, Jul 4, 2014 at 7:28 PM, Rameez T= honnakkal <ssrameez@gmail.com> wrote:
Thanks Mark.
the p= rocedure you shared is useful. I think I have missed the nodetool rebuild c= ommand.
I am trying it out in a non-prod environment.

The num_tokens is set to 1 and initial_token is set to different values (mi= ne is a 6 node cluster with 3 in each datacenter).
Tried a rollin= g restart of the cluster. That didn't help.
Tried a cold rest= art of the cluster. That also didn't work.

I will try the nodetool rebuild and see whether any change.
<= br>Thanks,
rameez


=
On Fri, Jul 4, 2014 at 7:19 PM, Mark Reddy <= span dir=3D"ltr"><mark.reddy@boxever.com> wrote:
Hi=C2=A0Rameez,

I have never done a migr= ation from vnodes to non-vnodes however I would imagine that the=C2=A0proce= dure=C2=A0would be the same as its counterpart. As always testing in dev sh= ould be done first.

To move from vnodes to non-vodes I would add a new datace= nter to the cluster with vnodes disabled and rebuild from your vnode cluste= r.



Ma= rk


On Fri, Jul 4, 2014 at 2:43 PM, Rameez T= honnakkal <ssrameez@gmail.com> wrote:
hello Team,

I am looking for = standard operating procedure to disable vnode in a production cluster.
=
This is to enable solr which doesn't work with a cassandra cluste= r having vnode enabled.

Any suggestions/

Thanks,
Rameez





--001a1135f2001eca7d04fd5f1ac4--