Mailing-List: contact user-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@cassandra.apache.org
Received-SPF: pass (athena.apache.org: domain of owenzhang1990@gmail.com
 designates 209.85.210.48 as permitted sender)
Message-ID: <510E3CD5.2070009@gmail.com>
Date: Sun, 03 Feb 2013 18:32:53 +0800
From: Manu Zhang <owenzhang1990@gmail.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
 rv:17.0) Gecko/20130106 Thunderbird/17.0.2
MIME-Version: 1.0
To: user@cassandra.apache.org
Subject: Re: Upgrade to Cassandra 1.2
References: 
 <CAGiE6h__DNqte+cnQ9fkQeDsN2tv1S88nczHZWW60ZrASDCeoQ@mail.gmail.com>
In-Reply-To: 
 <CAGiE6h__DNqte+cnQ9fkQeDsN2tv1S88nczHZWW60ZrASDCeoQ@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit

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 
over the ring).