Return-Path: Delivered-To: apmail-cassandra-user-archive@www.apache.org Received: (qmail 4262 invoked from network); 17 Mar 2010 20:53:29 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 17 Mar 2010 20:53:29 -0000 Received: (qmail 54784 invoked by uid 500); 17 Mar 2010 20:53:28 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 54769 invoked by uid 500); 17 Mar 2010 20:53:28 -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 54756 invoked by uid 99); 17 Mar 2010 20:53:28 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 17 Mar 2010 20:53:28 +0000 X-ASF-Spam-Status: No, hits=-1.1 required=10.0 tests=AWL,RCVD_IN_DNSWL_NONE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of bburruss@real.com designates 207.188.23.4 as permitted sender) Received: from [207.188.23.4] (HELO kal-el.real.com) (207.188.23.4) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 17 Mar 2010 20:53:23 +0000 Received: from seacas01.corp.real.com ([::ffff:192.168.139.56]) (TLS: TLSv1/SSLv3,128bits,AES128-SHA) by kal-el.real.com with esmtp; Wed, 17 Mar 2010 13:53:03 -0700 id 00080006.4BA1412F.00005F8A Received: from [172.21.131.225] (192.168.198.6) by seacas01.corp.real.com (192.168.139.56) with Microsoft SMTP Server id 8.2.176.0; Wed, 17 Mar 2010 13:53:03 -0700 Message-ID: <4BA1412E.8070108@real.com> Date: Wed, 17 Mar 2010 13:53:02 -0700 From: "B. Todd Burruss" User-Agent: Thunderbird 2.0.0.23 (X11/20090817) MIME-Version: 1.0 To: "user@cassandra.apache.org" Subject: Re: upgrade path 0.5.1 to 0.6.X References: In-Reply-To: Content-Type: text/plain; charset="ISO-8859-1"; format=flowed Content-Transfer-Encoding: 7bit Old-Return-Path: bburruss@real.com i see this in the upgrade notes: - 0.6 network traffic is not compatible with earlier versions. You will need to shut down all your nodes at once, upgrade, then restart. is there a plan to version the protocol used so new versions should be compatible with older ones until deprecated? Jonathan Ellis wrote: > upgrading is always covered in NEWS, e.g. > https://svn.apache.org/repos/asf/cassandra/branches/cassandra-0.6/NEWS.txt > > On Wed, Mar 17, 2010 at 3:21 PM, Joseph Stein wrote: > >> since it looks like 0.6.X is making its way towards GA, what is the >> data migration path for folks running 0.5.1? thanks....trying to >> decide if to go to production with 0.6 beta3 or 0.5.1 and upgrade. >> >> /* >> Joe Stein >> http://www.linkedin.com/in/charmalloc >> */ >> >>