From user-return-26176-apmail-cassandra-user-archive=cassandra.apache.org@cassandra.apache.org Wed May 16 02:09:32 2012 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 3E88096C5 for ; Wed, 16 May 2012 02:09:32 +0000 (UTC) Received: (qmail 67072 invoked by uid 500); 16 May 2012 02:09:30 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 67048 invoked by uid 500); 16 May 2012 02:09:30 -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 67037 invoked by uid 99); 16 May 2012 02:09:29 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 16 May 2012 02:09:29 +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 (nike.apache.org: domain of yulinyen@gmail.com designates 209.85.212.172 as permitted sender) Received: from [209.85.212.172] (HELO mail-wi0-f172.google.com) (209.85.212.172) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 16 May 2012 02:09:22 +0000 Received: by wibhj8 with SMTP id hj8so2598628wib.7 for ; Tue, 15 May 2012 19:09:02 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=DsRdMjNqsC3cccCRCCHtLzxPKtXcrGJjEmf7tjyz8uo=; b=Wu4il4mwTsUL2jQBv17HTWcC5R19gjOrVMoxTet5okfMD26DPa9A4CHlnlIRZ8EYL7 uzMefiwaPatLXkiOrTzG8CH+MATWbSaBwew2lEeojI75GiLK3jsGuuGIqVWFKwGBzYuy fyw3shm7CjMIFWIV3C+dUNwoim2I639An/UCXzsRhg/0y5ytPMjgsXUti8kj1RRxLUQW dGuhxADrwe6G2/f2dTQxg06T1f3u3Lx88jT5cKEAgwtI/HZxIX+oCMLaywwTyOZPbeec IhVs6qGy80tE00a8XqiuMD08d9HByINsM4IuQPMPDamcyl2AFwWDD7CQzZ1brbx+pq6y kBqw== MIME-Version: 1.0 Received: by 10.216.135.234 with SMTP id u84mr755451wei.108.1337134142227; Tue, 15 May 2012 19:09:02 -0700 (PDT) Received: by 10.223.88.20 with HTTP; Tue, 15 May 2012 19:09:02 -0700 (PDT) Date: Wed, 16 May 2012 10:09:02 +0800 Message-ID: Subject: Is nodetool upgradesstables a necessary step for upgrading from 0.8 to 1.0. From: Boris Yen To: user@cassandra.apache.org Content-Type: multipart/alternative; boundary=0016e6dd98969085be04c01dcdad --0016e6dd98969085be04c01dcdad Content-Type: text/plain; charset=ISO-8859-1 Hi, Our cluster is currently running on 0.8.10, we plan on upgrading it to 1.0.x. We read the document from the datastax website, the final step is to use nodetool upgradesstables. Since this command might take time to finish, I wonder if this step could be skip? if I do not upgrade the sstables what is going to happen? Thanks Boris --0016e6dd98969085be04c01dcdad Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hi,

Our cluster is currently running on 0.8.10, we plan = on upgrading it to 1.0.x. We read the document from the datastax website, t= he final step is to use nodetool upgradesstables. Since this command might = take time to finish, I wonder if this step could be skip? if I do not upgra= de the sstables what is going to happen?

Thanks
Boris
--0016e6dd98969085be04c01dcdad--