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 597361067A for ; Wed, 3 Jul 2013 11:57:16 +0000 (UTC) Received: (qmail 61014 invoked by uid 500); 3 Jul 2013 11:57:13 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 61004 invoked by uid 500); 3 Jul 2013 11:57:13 -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 60996 invoked by uid 99); 3 Jul 2013 11:57:12 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 03 Jul 2013 11:57:12 +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 mightye@gmail.com designates 209.85.215.43 as permitted sender) Received: from [209.85.215.43] (HELO mail-la0-f43.google.com) (209.85.215.43) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 03 Jul 2013 11:57:07 +0000 Received: by mail-la0-f43.google.com with SMTP id gw10so34925lab.16 for ; Wed, 03 Jul 2013 04:56:46 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type; bh=LkuZXLWzz8akrZR6g7nJX/N7GOPmjrTd9fxXklHzh0I=; b=LmItg0Bx8CcaAx5i+Q7k9DpcN4PZgeGV0kUU/pYEOuuQGdDGJLIPx7aKm1PwS8Bp+/ 8ZpLfSH7yhmaZbjZ+PWx9QsrM9hYlrqGsqWLWc52/5Fyeo+RV8W4EnLQCdlo5/+ah51i YCEb3mQ99Ht756YyMDxfLAMqSjM6gtlHU2JdjAlrUsFssElfAZq3ywt3KsN0+6f3TNxO zSkgygmsk5bsFzHd5rITjCH9wvoKR8/738+TUJYIugcgifLrnpjm3d4zw67ik2Os2TaR Bto6W/6OquNKLjwsHsJNL5YTxdJqnaJZtw1SMX7qLq0BkiEYenLg1ulE8PuBaKMIBBzp grfA== X-Received: by 10.152.88.5 with SMTP id bc5mr238117lab.81.1372852606365; Wed, 03 Jul 2013 04:56:46 -0700 (PDT) MIME-Version: 1.0 Received: by 10.152.128.194 with HTTP; Wed, 3 Jul 2013 04:56:26 -0700 (PDT) In-Reply-To: <2F77FA13-FE1C-4989-9719-7B6A2C7A5B50@grapheffect.com> References: <2F77FA13-FE1C-4989-9719-7B6A2C7A5B50@grapheffect.com> From: Eric Stevens Date: Wed, 3 Jul 2013 07:56:26 -0400 Message-ID: Subject: Re: columns disappearing intermittently To: user@cassandra.apache.org Content-Type: multipart/alternative; boundary=001a11c22578ee754304e09a27f8 X-Virus-Checked: Checked by ClamAV on apache.org --001a11c22578ee754304e09a27f8 Content-Type: text/plain; charset=UTF-8 I wonder if one particular node is having trouble; when you notice the missing column, what happens if you execute the read manually from cqlsh or cassandra-cli independently directly on each node? On Wed, Jul 3, 2013 at 2:00 AM, Blake Eggleston wrote: > Hi All, > > We're having a problem with our cassandra cluster and are at a loss as to > the cause. > > We have what appear to be columns that disappear for a little while, then > reappear. The rest of the row is returned normally during this time. This > is, of course, very disturbing, and is wreaking havoc with our application. > > A bit more info about what's happening: > > We are repeatedly executing the same query against our cluster. Every so > often, one of the columns will disappear from the row and will remain gone > for some time. Then after continually executing the same query, the column > will come back. The queries are being executed against a 3 node cluster, > with a replication factor of 3, and all reads and writes are done with a > quorum consistency level. > > We upgraded from cassandra 1.1.12 to 1.2.6 last week, but only started > seeing issues this morning. > > Has anyone had a problem like this before, or have any idea what might be > causing it? --001a11c22578ee754304e09a27f8 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
I wonder if one particular node is having trouble; when yo= u notice the missing column, what happens if you execute the read manually = from cqlsh or cassandra-cli independently directly on each node? =C2=A0


On Wed, Jul 3, 2013 at 2:00 AM, Blake Eg= gleston <blake@grapheffect.com> wrote:
Hi All,

We're having a problem with our cassandra cluster and are at a loss as = to the cause.

We have what appear to be columns that disappear for a little while, then r= eappear. The rest of the row is returned normally during this time. This is= , of course, very disturbing, and is wreaking havoc with our application.
A bit more info about what's happening:

We are repeatedly executing the same query against our cluster. Every so of= ten, one of the columns will disappear from the row and will remain gone fo= r some time. Then after continually executing the same query, the column wi= ll come back. The queries are being executed against a 3 node cluster, with= a replication factor of 3, and all reads and writes are done with a quorum= consistency level.

We upgraded from cassandra 1.1.12 to 1.2.6 last week, but only started seei= ng issues this morning.

Has anyone had a problem like this before, or have any idea what might be c= ausing it?

--001a11c22578ee754304e09a27f8--