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 6E87646F6 for ; Fri, 27 May 2011 11:59:38 +0000 (UTC) Received: (qmail 87379 invoked by uid 500); 27 May 2011 11:59:36 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 87356 invoked by uid 500); 27 May 2011 11:59:36 -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 87348 invoked by uid 99); 27 May 2011 11:59:36 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 27 May 2011 11:59:36 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of sylvain@datastax.com designates 209.85.161.172 as permitted sender) Received: from [209.85.161.172] (HELO mail-gx0-f172.google.com) (209.85.161.172) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 27 May 2011 11:59:30 +0000 Received: by gxk19 with SMTP id 19so925196gxk.31 for ; Fri, 27 May 2011 04:59:09 -0700 (PDT) MIME-Version: 1.0 Received: by 10.236.184.41 with SMTP id r29mr2826532yhm.0.1306497548864; Fri, 27 May 2011 04:59:08 -0700 (PDT) Received: by 10.236.103.2 with HTTP; Fri, 27 May 2011 04:59:08 -0700 (PDT) X-Originating-IP: [88.183.33.171] In-Reply-To: References: Date: Fri, 27 May 2011 13:59:08 +0200 Message-ID: Subject: Re: Corrupted Counter Columns From: Sylvain Lebresne To: user@cassandra.apache.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable On Thu, May 26, 2011 at 2:21 PM, Utku Can Top=E7u wrote= : > Hello, > > I'm using the the 0.8.0-rc1, with RF=3D2 and 4 nodes. > > Strangely counters are corrupted. Say, the actual value should be : 51664 > and the value that cassandra sometimes outputs is: either 51664 or 186510= 01. What does sometimes means in that context ? Is it like some query returns the former and some other the latter ? Does it alternate in the value returned despite no write coming in or does this at least stabilize to one of those value. Could you give more details on how this manifests itself. Does it depends on which node you connect to for the request for instance, does querying at QUORUM solves it ? > > And I have no idea on how to diagnose the problem or reproduce it. > > Can you help me in fixing this issue? > > Regards, > Utku >