Return-Path: Delivered-To: apmail-cassandra-user-archive@www.apache.org Received: (qmail 21699 invoked from network); 11 Jan 2011 17:59:50 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 11 Jan 2011 17:59:50 -0000 Received: (qmail 98948 invoked by uid 500); 11 Jan 2011 17:59:47 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 98839 invoked by uid 500); 11 Jan 2011 17:59:47 -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 98831 invoked by uid 99); 11 Jan 2011 17:59:47 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 11 Jan 2011 17:59:47 +0000 X-ASF-Spam-Status: No, hits=1.5 required=10.0 tests=FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,RFC_ABUSE_POST,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of daveviner@gmail.com designates 209.85.215.44 as permitted sender) Received: from [209.85.215.44] (HELO mail-ew0-f44.google.com) (209.85.215.44) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 11 Jan 2011 17:59:39 +0000 Received: by ewy8 with SMTP id 8so9658337ewy.31 for ; Tue, 11 Jan 2011 09:59:19 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:date:message-id :subject:from:to:content-type; bh=zZhtJtzaP1yG4WqcMNrQMNqzRvzOhFmiOzkBEF/7mtM=; b=Q3JiTVmAixFfF+lVtAdniQ9sXvXpBhvE3B9TUxco2Srs80YaInpMUPdJxhOzPRPQTc Gxc9PwUyyhH4aQlwH3j5ZHm0bkLap4mukd6jVlsgn8/xJZfAwi6iRZoyMMDrMQRo+Cil SK53SoEoOULuzEnw+02WDtNKVsjL+FysTJaHo= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=S2XnJBSIE8ve6HRyjFR072FUsEawNUByI7Cwu6vS8HzUIJE/+MuAjFqUse4Gs2tqeQ wp9xL+gohm315gFegZstX/zoAj2eABQ8Xw8Pwg/K2YNwQKM9ucWHao89HhDzEEmFPSuH cp4lmFbCSkExfiGfnaeioaEyM3m0/2f0cMnew= MIME-Version: 1.0 Received: by 10.213.7.65 with SMTP id c1mr3102192ebc.87.1294768758857; Tue, 11 Jan 2011 09:59:18 -0800 (PST) Received: by 10.14.125.196 with HTTP; Tue, 11 Jan 2011 09:59:18 -0800 (PST) Date: Tue, 11 Jan 2011 09:59:18 -0800 Message-ID: Subject: upgrading to 0.7 from 0.6.x From: Dave Viner To: user Content-Type: multipart/alternative; boundary=0015174c1310f022a8049995d789 X-Virus-Checked: Checked by ClamAV on apache.org --0015174c1310f022a8049995d789 Content-Type: text/plain; charset=ISO-8859-1 Hi all, I'm reading the upgrading notes in the NEWS.txt file, but I don't see how/where the data from the 0.6 cluster is actually migrated. Current, in the file, it says: The process to upgrade is: 1) run "nodetool drain" on _each_ 0.6 node. When drain finishes (log message "Node is drained" appears), stop the process. 2) Convert your storage-conf.xml to the new cassandra.yaml using "bin/config-converter". 3) Rename any of your keyspace or column family names that do not adhere to the '^\w+' regex convention. 4) Start up your cluster with the 0.7 version. 5) Initialize your Keyspace and ColumnFamily definitions using "bin/schematool import". _You only need to do this to one node_. I assume the instructions in step 5 refer to new 0.7 node, not the 0.6 node. Is the idea to install 0.7 alongside the 0.6 instance or to replace the entire machine/node with a new node running 0.7? If so, is there a step 1b, which is "install 0.7 code & executables" ? Thanks Dave Viner --0015174c1310f022a8049995d789 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hi all,

I'm reading the upgrading = notes in the NEWS.txt file, but I don't see how/where the data from the= 0.6 cluster is actually migrated.

Current, in the file, it says:

The process to upgrade is:
    1) run "nodetool drain" on _each_ 0.6 node.  When drain finis=
hes (log
       message "Node is drained" appears), stop the process.
    2) Convert your storage-conf.xml to the new cassandra.yaml using=20
       "bin/config-converter". =20
    3) Rename any of your keyspace or column family names that do not adher=
e
       to the '^\w+' regex convention.
    4) Start up your cluster with the 0.7 version.
    5) Initialize your Keyspace and ColumnFamily definitions using=20
       "bin/schematool <host> <jmxport> import".  _Yo=
u only need to do=20
       this to one node_.
I assume the =
instructions in step 5 refer to new 0.7 node, not the 0.6 node.

Is the idea to install 0.7 alongside the 0.6 instance or to replace the=
 entire machine/node with a new node running 0.7?  If so, is there a step 1=
b, which is "install 0.7 code & executables" ?

Thanks
Dave Viner
--0015174c1310f022a8049995d789--