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 A2D118EFF for ; Fri, 9 Sep 2011 03:59:20 +0000 (UTC) Received: (qmail 42625 invoked by uid 500); 9 Sep 2011 03:59:18 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 41966 invoked by uid 500); 9 Sep 2011 03:58:58 -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 41935 invoked by uid 99); 9 Sep 2011 03:58:56 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 09 Sep 2011 03:58:56 +0000 X-ASF-Spam-Status: No, hits=2.2 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (nike.apache.org: local policy) Received: from [209.85.212.43] (HELO mail-vw0-f43.google.com) (209.85.212.43) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 09 Sep 2011 03:58:49 +0000 Received: by vws10 with SMTP id 10so736587vws.30 for ; Thu, 08 Sep 2011 20:58:29 -0700 (PDT) MIME-Version: 1.0 Received: by 10.52.187.40 with SMTP id fp8mr933186vdc.42.1315540708812; Thu, 08 Sep 2011 20:58:28 -0700 (PDT) Received: by 10.52.107.193 with HTTP; Thu, 8 Sep 2011 20:58:28 -0700 (PDT) In-Reply-To: References: Date: Thu, 8 Sep 2011 20:58:28 -0700 Message-ID: Subject: Re: Anybody out there using 0.8 in production From: Chris Goffinet To: user@cassandra.apache.org Content-Type: multipart/alternative; boundary=bcaec547cb7da2e82904ac7a305e X-Virus-Checked: Checked by ClamAV on apache.org --bcaec547cb7da2e82904ac7a305e Content-Type: text/plain; charset=ISO-8859-1 Twitter runs 0.8 in production/closer to trunk. No big issues from us. On Thu, Sep 8, 2011 at 8:53 PM, Eric Czech wrote: > We just migrated from .7.5 to .8.4 in our production environment and it was > definitely the least painful transition yet (coming all the way from the .4 > release series). It's been about a week for us but so far so good. > > > On Thu, Sep 8, 2011 at 9:25 PM, Dominic Williams < > dwilliams@fightmymonster.com> wrote: > >> Hi I've just migrated to 0.8.5 and from first looks it is a giant leap >> forward >> - better use of CPU and memory >> - able to scrub files previously unfixable on 0.7.6-2 >> etc >> >> >> On 9 September 2011 01:45, Anthony Ikeda wrote: >> >>> We plan to and have been using it in Dev and QA. There are some bugs that >>> have been fixed that we are looking forward to in 0.8.5 and probably that >>> would be the better build for production (there is a quorum bug that we will >>> need). >>> >>> Otherwise no other 0.8 issues that we are aware of. We did go through a >>> long analysis of properly configuring connection options and getting the >>> server setup right but DataStax were abe to support us and get us sorted. >>> >>> Anthony >>> >>> >>> On Thu, Sep 8, 2011 at 2:44 PM, Anand Somani wrote: >>> >>>> Hi >>>> >>>> Currently we are using 0.7.4 and was wondering if I should upgrade to >>>> 0.7.8/9 or move to 0.8? Is anybody using 0.8 in production and what is their >>>> experience? >>>> >>>> Thanks >>>> >>> >>> >> > --bcaec547cb7da2e82904ac7a305e Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Twitter runs 0.8 in production/closer to trunk. No big issues from us.
=

On Thu, Sep 8, 2011 at 8:53 PM, Eric Cze= ch <eric@next= bigsound.com> wrote:
We just migrated from .7.5 to .8.4 in our p= roduction environment and it was definitely the least painful transition ye= t (coming all the way from the .4 release series). =A0It's been about a= week for us but so far so good. =A0


On Thu, Sep 8, 2011 at 9:25 PM, Dominic Will= iams <dwilliams@fightmymonster.com> wrote:
Hi I've just migrated to 0.8.5 and from first looks it is a giant leap = forward
- better use of CPU and memory
- able to scrub files = previously unfixable on 0.7.6-2
etc


On 9 September 2011 01:45, Anthony Ikeda <anthony.ikeda.dev@gmai= l.com> wrote:
We plan to and have been using it in Dev and QA. There are some bugs that h= ave been fixed that we are looking forward to in 0.8.5 and probably that wo= uld be the better build for production (there is a quorum bug that we will = need).

Otherwise no other 0.8 issues that we are aware of. We did g= o through a long analysis of properly configuring connection options and ge= tting the server setup right but DataStax were abe to support us and get us= sorted.

Anthony


On= Thu, Sep 8, 2011 at 2:44 PM, Anand Somani <meatforums@gmail.com>= ; wrote:
Hi

Currently we are using 0.7.4 and was wondering if I should upgra= de to 0.7.8/9 or move to 0.8? Is anybody using 0.8 in production and what i= s their experience?

Thanks




--bcaec547cb7da2e82904ac7a305e--