incubator-cassandra-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hiller, Dean" <>
Subject Re: is upgradesstables required for 1.1.4 to 1.2.2? (I don't think it is)
Date Wed, 27 Feb 2013 19:31:04 GMT
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

Quote from Aaron...
In pre 1.2 add these jvm startup params



On 2/27/13 12:00 PM, "Michael Kjellman" <> wrote:

>Yes, it's required between majors. Which your upgrade would be.
>On 2/27/13 10:54 AM, "Hiller, Dean" <> wrote:
>>My script to upgrade our first node in QA is thus (basically, snapshot,
>>drain, stop, then switch over then start)Š
>>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'
>>#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
>># access to the opt directory.
>>ssh root@$NODE <<\EOF
>>   rm /opt/cassandra
>>   ln -s /opt/cassandra-1.2.2 /opt/cassandra
>>#We should start cassandra ourselves 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
>Copy, by Barracuda, helps you store, protect, and share all your amazing
>things. Start today:

View raw message