incubator-cassandra-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Charles Brophy <cbro...@zulily.com>
Subject Invalid Counter Shard errors?
Date Thu, 31 May 2012 15:20:28 GMT
Hi guys,

We're running a three node cluster of cassandra 1.1 servers, originally
1.0.7 and immediately after the upgrade the error logs of all three servers
began filling up with the following message:

ERROR [ReplicateOnWriteStage:177] 2012-05-31 08:17:02,236
CounterContext.java (line 381) invalid counter shard detected;
(3438afc0-7e71-11e1-0000-da5a9d01e7f7, 3, 4) and
(3438afc0-7e71-11e1-0000-da5a9d01e7f7, 3, 7) differ only in count; will
pick highest to self-heal; this indicates a bug or corruption generated a
bad counter shard

ERROR [ValidationExecutor:20] 2012-05-31 08:17:01,570 CounterContext.java
(line 381) invalid counter shard detected;
(343cf580-7e71-11e1-0000-ebc411012bff, 14, 27) and
(343cf580-7e71-11e1-0000-ebc411012bff, 14, 21) differ only in count; will
pick highest to self-heal; this indicates a bug or corruption generated a
bad counter shard

The counts change but the errors are constant. What is the best course of
action? Google only turns up the source code for these errors.

Thanks!
Charles

Mime
View raw message