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 01BE3EAF6 for ; Tue, 12 Feb 2013 19:03:06 +0000 (UTC) Received: (qmail 24261 invoked by uid 500); 12 Feb 2013 19:03:03 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 24237 invoked by uid 500); 12 Feb 2013 19:03:03 -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 24228 invoked by uid 99); 12 Feb 2013 19:03:03 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 12 Feb 2013 19:03:03 +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 (athena.apache.org: domain of daning@netseer.com designates 209.85.217.169 as permitted sender) Received: from [209.85.217.169] (HELO mail-lb0-f169.google.com) (209.85.217.169) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 12 Feb 2013 19:02:58 +0000 Received: by mail-lb0-f169.google.com with SMTP id m4so361889lbo.28 for ; Tue, 12 Feb 2013 11:02:37 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:content-type:x-gm-message-state; bh=R6bTAjrmnIsRkTpS8hkPmKyWswB/s30Ux7aGCV33U10=; b=VSdBt1RbatwMbqIE8u8igWdFkPSpkg5ZnQGjkj0uTubH4P7cQlNKBhVdvwqf6KFfk/ HfduQ/BOZM0QQ7E7TYg48zKEgRm5Ha1Y8TvtAiH8L4psa8BdYDZ8Q/R+JFmuUG3djlHL M8bLPGFoi/WZlveho5fhAj3Cn/xZj4+dqEe+3fHErpb2FWSzdiezp5wBynkwk44/0JI6 edjbSMgw8dFgg2+9vjAYrKmpuQ863M//GExlU4CG/A1clLcwS1cUWPsKtxfmW6c1/fZa 2MAKcF3wuub2pMrYR5M0zqOG20WPFEVqD8hyPnI837EQYiRsWNef9Rj3yJHaozIdwiNG rNrw== MIME-Version: 1.0 X-Received: by 10.152.132.138 with SMTP id ou10mr5426721lab.56.1360695756838; Tue, 12 Feb 2013 11:02:36 -0800 (PST) Received: by 10.114.99.10 with HTTP; Tue, 12 Feb 2013 11:02:36 -0800 (PST) In-Reply-To: <25361E27-9E2B-4D8D-8C5A-ABDF6C679FC6@thelastpickle.com> References: <510E3CD5.2070009@gmail.com> <380D12D7-4DC6-41DC-B8FA-A721250FCDAD@thelastpickle.com> <25361E27-9E2B-4D8D-8C5A-ABDF6C679FC6@thelastpickle.com> Date: Tue, 12 Feb 2013 11:02:36 -0800 Message-ID: Subject: Re: Upgrade to Cassandra 1.2 From: Daning Wang To: user@cassandra.apache.org Content-Type: multipart/alternative; boundary=f46d042d051c3bd90404d58babb7 X-Gm-Message-State: ALoCoQnss31EYnpUfwAHGAXrG+d9iT3Sd/R9xXhxuD0OPUECjTqZoNJZOg7vcX6nYGuDb/v2txz/ X-Virus-Checked: Checked by ClamAV on apache.org --f46d042d051c3bd90404d58babb7 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable No, I did not run shuffle since the upgrade was not successful. what do you mean "reverting the changes to num_tokens and inital_token"? set num_tokens=3D1? initial_token should be ignored since it is not bootstrap. right? Thanks, Daning On Tue, Feb 12, 2013 at 10:52 AM, aaron morton wro= te: > Were you upgrading to 1.2 AND running the shuffle or just upgrading to > 1.2? > > If you have not run shuffle I would suggest reverting the changes to > num_tokens and inital_token. This is a guess because num_tokens is only > used at bootstrap. > > Just get upgraded to 1.2 first, then do the shuffle when things are > stable. > > Cheers > > ----------------- > Aaron Morton > Freelance Cassandra Developer > New Zealand > > @aaronmorton > http://www.thelastpickle.com > > On 12/02/2013, at 2:55 PM, Daning Wang wrote: > > Thanks Aaron. > > I tried to migrate existing cluster(ver 1.1.0) to 1.2.1 but failed. > > - I followed http://www.datastax.com/docs/1.2/install/upgrading, have > merged cassandra.yaml, with follow parameter > > num_tokens: 256 > #initial_token: 0 > > the initial_token is commented out, current token should be obtained from > system schema > > - I did rolling upgrade, during the upgrade, I got "Borken Pipe" error > from the nodes with old version, is that normal? > > - After I upgraded 3 nodes(still have 5 to go), I found it is total wrong= , > the first node upgraded owns 99.2 of ring > > [cassy@d5:/usr/local/cassy conf]$ ~/bin/nodetool -h localhost status > Datacenter: datacenter1 > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > Status=3DUp/Down > |/ State=3DNormal/Leaving/Joining/Moving > -- Address Load Tokens Owns Host ID > Rack > DN 10.210.101.117 45.01 GB 254 99.2% > f4b6afe3-7e2e-4c61-96e8-12a529a31373 rack1 > UN 10.210.101.120 45.43 GB 256 0.4% > 0fd912fb-3187-462b-8c8a-7d223751b649 rack1 > UN 10.210.101.111 27.08 GB 256 0.4% > bd4c37bc-07dd-488b-bfab-e74e32c26f6e rack1 > > > What was wrong? please help. I could provide more information if you need= . > > Thanks, > > Daning > > > > On Mon, Feb 4, 2013 at 9:16 AM, aaron morton wro= te: > >> There is a command line utility in 1.2 to shuffle the tokens=85 >> >> http://www.datastax.com/dev/blog/upgrading-an-existing-cluster-to-vnodes >> >> $ ./cassandra-shuffle --help >> Missing sub-command argument. >> Usage: shuffle [options] >> >> Sub-commands: >> create Initialize a new shuffle operation >> ls List pending relocations >> clear Clear pending relocations >> en[able] Enable shuffling >> dis[able] Disable shuffling >> >> Options: >> -dc, --only-dc Apply only to named DC (create only) >> -tp, --thrift-port Thrift port number (Default: 9160) >> -p, --port JMX port number (Default: 7199) >> -tf, --thrift-framed Enable framed transport for Thrift (Default: >> false) >> -en, --and-enable Immediately enable shuffling (create only) >> -H, --help Print help information >> -h, --host JMX hostname or IP address (Default: localhos= t) >> -th, --thrift-host Thrift hostname or IP address (Default: JMX >> host) >> >> Cheers >> >> ----------------- >> Aaron Morton >> Freelance Cassandra Developer >> New Zealand >> >> @aaronmorton >> http://www.thelastpickle.com >> >> On 3/02/2013, at 11:32 PM, Manu Zhang wrote: >> >> On Sun 03 Feb 2013 05:45:56 AM CST, Daning Wang wrote: >> >> I'd like to upgrade from 1.1.6 to 1.2.1, one big feature in 1.2 is >> that it can have multiple tokens in one node. but there is only one >> token in 1.1.6. >> >> how can I upgrade to 1.2.1 then breaking the token to take advantage >> of this feature? I went through this doc but it does not say how to >> change the num_token >> >> http://www.datastax.com/docs/1.2/install/upgrading >> >> Is there other doc about this upgrade path? >> >> Thanks, >> >> Daning >> >> >> I think for each node you need to change the num_token option in >> conf/cassandra.yaml (this only split the current range into num_token >> parts) and run the bin/cassandra-shuffle command (this spread it all ove= r >> the ring). >> >> >> > > --f46d042d051c3bd90404d58babb7 Content-Type: text/html; charset=windows-1252 Content-Transfer-Encoding: quoted-printable No, I did not run shuffle since the upgrade was not successful.=A0

=
what do you mean "reverting the changes to num_tokens and i= nital_token"? set num_tokens=3D1? initial_token should be ignored sinc= e it is not bootstrap. right?

Thanks,

Daning

On Tue, Feb 12, 2013 at 10:52 AM, aaron morton <a= aron@thelastpickle.com> wrote:
Were you= upgrading to 1.2 AND running the shuffle or just upgrading to 1.2?=A0
=
If you have not run shuffle I would suggest reverting the change= s to num_tokens and inital_token. This is a guess because num_tokens is onl= y used at bootstrap.=A0

Just get upgraded to 1.2 f= irst, then do the shuffle when things are stable.=A0

Cheers

-----------------
Aaron Morton
Freelance Cassandra= Developer
New Zealand


On 12/02/2013, at 2:55 PM, Danin= g Wang <daning@n= etseer.com> wrote:

Thanks Aa= ron.

I tried to migrate existing cluster(ver 1.1.0) to 1.2.1= but failed.

- I followed=A0http://www.datas= tax.com/docs/1.2/install/upgrading,=A0have merged cassandra.yaml, with = follow parameter

num_tokens: 256
#initial_token: 0
<= /div>

the initial_token is commented out, current token = should be obtained from system schema

- I did roll= ing upgrade, during the upgrade, I got "Borken Pipe" error from t= he nodes with old version, is that normal?

- After I upgraded 3 nodes(still have 5 to go), I found= it is total wrong, the first node upgraded owns 99.2 of ring
[cassy@d5:/usr/local/cassy conf]$ =A0~/bin/nodetool -h loc= alhost status
Datacenter: datacenter1
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
Status=3DUp/Down
|/ S= tate=3DNormal/Leaving/Joining/Moving
-- =A0Address =A0 =A0 =A0 = =A0 =A0 Load =A0 =A0 =A0 Tokens =A0Owns =A0 Host ID =A0 =A0 =A0 =A0 =A0 =A0= =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 Rack
DN =A010.210.101.117 =A0 =A045.01 GB =A0 254 =A0 =A0 99.2% =A0f4b6afe3= -7e2e-4c61-96e8-12a529a31373 =A0rack1
UN =A010.210.101.120 =A0 = =A045.43 GB =A0 256 =A0 =A0 0.4% =A0 0fd912fb-3187-462b-8c8a-7d223751b649 = =A0rack1
UN =A010.210.101.111 =A0 =A027.08 GB =A0 256 =A0 =A0 0.4= % =A0 bd4c37bc-07dd-488b-bfab-e74e32c26f6e =A0rack1


What was wrong? please help. I cou= ld provide more information if you need.

Thanks,

Daning



On Mon, Feb 4, 2013 at 9:16 AM, aaron morton <aaron@thelastpickle.c= om> wrote:
There is a command line utility in 1.2 = to shuffle the tokens=85

htt= p://www.datastax.com/dev/blog/upgrading-an-existing-cluster-to-vnodes

$ ./cassandra-shuffle --help
Missing sub= -command argument.
Usage: shuffle [options] <sub-command>

Sub-commands:
=A0create =A0 =A0 =A0 =A0 = =A0 Initialize a new shuffle operation
=A0ls =A0 =A0 =A0 =A0 =A0 =A0 =A0 List pending relocations
= =A0clear =A0 =A0 =A0 =A0 =A0 =A0Clear pending relocations
=A0en[a= ble] =A0 =A0 =A0 =A0 Enable shuffling
=A0dis[able] =A0 =A0 =A0 = =A0Disable shuffling

Options:
=A0-dc, =A0--only-dc =A0 =A0 =A0 =A0 =A0 Apply only to named DC (creat= e only)
=A0-tp, =A0--thrift-port =A0 =A0 =A0 Thrift port number (= Default: 9160)
=A0-p, =A0 --port =A0 =A0 =A0 =A0 =A0 =A0 =A0JMX p= ort number (Default: 7199)
=A0-tf, =A0--thrift-framed =A0 =A0 Enable framed transport for Thrift (Defa= ult: false)
=A0-en, =A0--and-enable =A0 =A0 =A0 =A0Immediately enable shuffling (c= reate only)
=A0-H, =A0 --help =A0 =A0 =A0 =A0 =A0 =A0 =A0Print he= lp information
=A0-h, =A0 --host =A0 =A0 =A0 =A0 =A0 =A0 =A0JMX h= ostname or IP address (Default: localhost)
=A0-th, =A0--thrift-host =A0 =A0 =A0 Thrift hostname or IP address (De= fault: JMX host)

Cheers

-----------------
Aaron Morton
Freelance Cassandra= Developer
New Zealand


On 3/02/2013, at 11:32 PM, Manu Zhang <owenzhang1990@gmail.com> w= rote:

On Sun 03 Feb 2013 05:45:56 AM CST= , Daning Wang wrote:
I'd like to upgrade from 1.1.6 to 1.2.1, one = big feature in 1.2 is
that it can have multiple tokens in one node. but = there is only one
token in 1.1.6.

how can I upgrade to 1.2.1 then= breaking the token to take advantage
of this feature? I went through this doc but it does not say how to
chan= ge the num_token

http://www.datastax.com/docs/1.2/install/upgr= ading

Is there other doc about this upgrade path?

Thanks,

Dani= ng

I think for each node you need to change the num_tok= en option in conf/cassandra.yaml (this only split the current range into nu= m_token parts) and run the bin/cassandra-shuffle command (this spread it al= l over the ring).




--f46d042d051c3bd90404d58babb7--