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 F0B9ED1C8 for ; Sat, 21 Jul 2012 06:19:12 +0000 (UTC) Received: (qmail 18397 invoked by uid 500); 21 Jul 2012 06:19:10 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 18297 invoked by uid 500); 21 Jul 2012 06:19:09 -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 18272 invoked by uid 99); 21 Jul 2012 06:19:08 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 21 Jul 2012 06:19:08 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=FSL_RCVD_USER,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of codeithere@gmail.com designates 209.85.160.44 as permitted sender) Received: from [209.85.160.44] (HELO mail-pb0-f44.google.com) (209.85.160.44) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 21 Jul 2012 06:19:02 +0000 Received: by pbcwy7 with SMTP id wy7so7645174pbc.31 for ; Fri, 20 Jul 2012 23:18:41 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=vjN5yVEESUuOyGx6drp3OFttMnUqY7KYEzpgLlGOjjY=; b=ruwDAIaTZAiviolBws8u3UfynASy1QGDjoEclgJVXDB624lRmjHM0HdGKRjAkEP5Hc zveyP3HTn3r/alIBgJvZkXzmz9xBAk6dnn4rh06gyKp1OyamZ4sU/cWsQIfZ4eRtW8Rh M8B+39TNnwBJbAdqA10XmhL056es6cziaEBVKB60osaD52asJDuuMpof0vvdsX1/xesY P8g2A7SDU4cZnmWVPXFZGa6fDiDXZqksNlpegpXDDCTag6scLT4OaBq1445mIeuhtd6w iPFfaoJeMwGoB1rjc3i4C4ffrroNBW0UrXpeA5nGLnrG8Yne11Y4+84WPql4xpHGkHpe FFJw== MIME-Version: 1.0 Received: by 10.68.218.7 with SMTP id pc7mr19411520pbc.88.1342851521678; Fri, 20 Jul 2012 23:18:41 -0700 (PDT) Received: by 10.143.141.15 with HTTP; Fri, 20 Jul 2012 23:18:41 -0700 (PDT) In-Reply-To: References: <0A1AC4A2-69B7-4228-A13F-FC769C0F072D@chacha.com> Date: Fri, 20 Jul 2012 23:18:41 -0700 Message-ID: Subject: Re: 0.8 --> 1.1 Upgrade: Any Issues? From: Code Box To: user@cassandra.apache.org Content-Type: multipart/alternative; boundary=e89a8ff244cfef8c2104c550fb19 --e89a8ff244cfef8c2104c550fb19 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable It has given me weird results in terms of performance. You can try with what Netflix is using they seem to be pretty happy with this version of Cassandra. http://techblog.netflix.com/2012/07/benchmarking-high-performance-io-with.h= tml On Fri, Jul 20, 2012 at 2:34 AM, aaron morton wrot= e: > Can a rolling upgrade be done or is it all-or-nothing? > > > Rolling upgrade, take a look at news=85. > https://github.com/apache/cassandra/blob/cassandra-1.1/NEWS.txt > > (my personal approach is to test in dev, and upgrade a single node for a > few hours to make sure everything is ok) > > Cheers > > ----------------- > Aaron Morton > Freelance Developer > @aaronmorton > http://www.thelastpickle.com > > On 20/07/2012, at 4:10 PM, Peter Schuller wrote: > > We currently have a 0.8 production cluster that I would like to upgrade t= o > > 1.1. Are there any know compatibility or upgrade issues between 0.8 and > 1.1? > > Can a rolling upgrade be done or is it all-or-nothing? > > > If you have lots of keys: > https://issues.apache.org/jira/browse/CASSANDRA-3820 > > -- > / Peter Schuller (@scode, http://worldmodscode.wordpress.com) > > > --e89a8ff244cfef8c2104c550fb19 Content-Type: text/html; charset=windows-1252 Content-Transfer-Encoding: quoted-printable It has given me weird results in terms of performance. You can try with wha= t Netflix is using they seem to be pretty happy with this version of Cassan= dra.


On Fri, Jul 20, 2012 at 2:34 AM, aa= ron morton <aaron@thelastpickle.com> wrote:
Can a rolling upgrade be done or i= s it all-or-nothing?

Rolling upgrade, take a look at news=85.
https://github.com/apache/cassandra/blob/cassandra-1.1/NEWS.tx= t

(my personal approach is to test in dev, and upgrade a singl= e node for a few hours to make sure everything is ok)=A0

Cheers

<= div style=3D"word-wrap:break-word">
-----------------
Aaron Morton
Freelance Deve= loper
@aaronmorton

On 20/07/2012, at 4:10 PM, Peter Schuller wrote:

We currently have a 0= .8 production cluster that I would like to upgrade to
1.1. Are there any know compatibility or upgrade issues between 0.8 and 1.1= ?
Can a rolling upgrade be done o= r is it all-or-nothing?

If you have lots of keys: https://issues.apache.org/jira/browse/CASSANDRA-3820

--
/ Peter Schuller (@scode, http://worldmodscode.wordpress.com)


--e89a8ff244cfef8c2104c550fb19--