Mailing-List: contact user-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@cassandra.apache.org
Received-SPF: pass (nike.apache.org: domain of rcoli@eventbrite.com designates
 209.85.216.171 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <78073DF1CF7E49EA8CF68C5C79F8FB30@keen.io>
References: <78073DF1CF7E49EA8CF68C5C79F8FB30@keen.io>
Date: Tue, 25 Jun 2013 11:18:24 -0700
Message-ID: 
 <CAEDUwd2urh6=gM7Qy7Pi44MQNRKErFtPsgpCLAbLeWeOhdkG8g@mail.gmail.com>
Subject: Re: Counter value becomes incorrect after several dozen reads &
 writes
From: Robert Coli <rcoli@eventbrite.com>
To: user@cassandra.apache.org
Content-Type: text/plain; charset=ISO-8859-1

On Mon, Jun 24, 2013 at 6:42 PM, Josh Dzielak <josh@keen.io> wrote:
> There is only 1 thread running this sequence, and consistency levels are set
> to ALL. The behavior is fairly repeatable - the unexpectation mutation will
> happen at least 10% of the time I run this program, but at different points.
> When it does not go awry, I can run this loop many thousands of times and
> keep the counter exact. But if it starts happening to a specific counter,
> the counter will never "recover" and will continue to maintain it's
> incorrect value even after successful subsequent writes.

Sounds like a corrupt counter shard. Hard to understand how it can
happen at ALL. If I were you I would file a JIRA including your repro
path...

=Rob