Mailing-List: contact user-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@cassandra.apache.org
Received-SPF: pass (nike.apache.org: domain of michalm@opera.com designates
 213.236.208.81 as permitted sender)
Message-ID: <512F03EF.7080303@opera.com>
Date: Thu, 28 Feb 2013 08:14:55 +0100
From: Michal Michalski <michalm@opera.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: is upgradesstables required for 1.1.4 to 1.2.2? (I don't think
 it is)
References: <CD53AED4.21957%Dean.Hiller@nrel.gov>
In-Reply-To: <CD53AED4.21957%Dean.Hiller@nrel.gov>
Content-Type: text/plain; charset=ISO-8859-2; format=flowed
Content-Transfer-Encoding: 8bit

I'm currently migrating 1.1.0 to 1.2.1 and on our small CI cluster, that 
I was testing some stuff on, it seems that it's not required to run 
upgradesstables (this doc doesn't mention about it too: 
http://www.datastax.com/docs/1.2/install/upgrading but the previous 
versions did). Of course I'd like to upgrade them sooner or later (in 
case of another C* upgrade or so), but for me it seems like it's just 
going to work ("Cassandra is able to read data files created by the 
previous version, but the inverse is not always true.") and compactions 
will slowly "convert" old-version SSTables to new ones if I don't do it 
manually.

M.

W dniu 27.02.2013 20:40, Hiller, Dean pisze:
> Hmmmm, wouldn't I have to run upgradesstables BEFORE I start the 1.2.2
> node?  But running upgradesstables as I recall required cassandra to be
> running.....so does it somehow understand the old format when it starts I
> suspect?
>
> I am thinking I just keep the node out of the ring while I run the
> upgradesstables, correct? But of course am not sure how to start a 1.2.2
> node such that it does not join the cluster.
>
> Thanks,
> Dean
>
> On 2/27/13 12:31 PM, "Hiller, Dean" <Dean.Hiller@nrel.gov> wrote:
>
>> Hmmm, I have this info from Aaron, but what about bringing up version
>> 1.2.2 with thrift off so I can run upgradesstables before I rejoin the
>> ring?
>>
>> Quote from Aaron...
>> In pre 1.2 add these jvm startup params
>>
>> -Dcassandra.join_ring=false
>> -Dcassandra.start_rpc=false
>>
>>
>>
>> Thanks,
>> Dean
>>
>> On 2/27/13 12:00 PM, "Michael Kjellman" <mkjellman@barracuda.com> wrote:
>>
>>> Yes, it's required between majors. Which your upgrade would be.
>>>
>>> On 2/27/13 10:54 AM, "Hiller, Dean" <Dean.Hiller@nrel.gov> wrote:
>>>
>>>> My script to upgrade our first node in QA is thus (basically, snapshot,
>>>> drain, stop, then switch over then start)�
>>>>
>>>> #!/bin/bash
>>>>
>>>> export NODE=$1
>>>> export VERSION=1.1.4
>>>> export USER=cassandra
>>>>
>>>> #NOTE: This script requires you have cassandra 1.2.2 in
>>>> /opt/cassandra-1.2.2 but
>>>> # feel free to modify if you like
>>>>
>>>> #Move the newest cassandra.yaml to the node
>>>> scp cassandra.yaml $USER@$NODE:/opt/cassandra/conf
>>>>
>>>> #As cassandra user, snapshot then drain the node
>>>> # and finally shut down cassandra on that node
>>>> ssh $USER@$NODE <<\EOF
>>>>    nodetool snapshot $VERSION
>>>>    nodetool drain
>>>>    pkill -f 'java.*cassandra'
>>>> EOF
>>>>
>>>> #Now, our .bashrc for cassandra has /opt/cassandra/bin in it's path
>>>> # so we unlink and the link to the new cassandra as root since only root
>>>> has
>>>> # access to the opt directory.
>>>> ssh root@$NODE <<\EOF
>>>>    rm /opt/cassandra
>>>>    ln -s /opt/cassandra-1.2.2 /opt/cassandra
>>>> EOF
>>>>
>>>> #We should start cassandra ourselves probably....so we can watch the
>>>> cluster as it joins the node
>>>> #especially for the very first node we do...
>>>> #Now as cassandra user, start up the cassandra node and then do manual
>>>> health checks
>>>> #ssh $USER@$NODE <<\EOF
>>>> #   cassandra
>>>> #EOF
>>>
>>>
>>> Copy, by Barracuda, helps you store, protect, and share all your amazing
>>>
>>> things. Start today: www.copy.com.
>>