[
https://issues.apache.org/jira/browse/CASSANDRA-4417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13669539#comment-13669539
]
Phil Pirozhkov commented on CASSANDRA-4417:
-------------------------------------------
Cassandra 1.2.5, single node dev local installation.
Schema:
{code}
CREATE TABLE reporting (
zoom int,
time timestamp,
total counter,
PRIMARY KEY (zoom, time)
)
WITH CLUSTERING ORDER BY (time ASC);
update reporting set total = total + 1 where zoom = 0 and time = 1234142142141;
update reporting set total = total + 1 where zoom = 1 and time = 1234142142141;
update reporting set total = total + 1 where zoom = 2 and time = 1234142142141;
{code}
Query: {code}select * from reporting where zoom=0;{code} may produce different
results, either rpc timeout either 'total' is null.
Nodetool repair does nothing and hangs time to time.
Chance to reproduce 50%.
Tried to change to batch commitlog mode, same result (but 10 times less
performant).
> invalid counter shard detected
> -------------------------------
>
> Key: CASSANDRA-4417
> URL: https://issues.apache.org/jira/browse/CASSANDRA-4417
> Project: Cassandra
> Issue Type: Bug
> Components: Core
> Affects Versions: 1.1.1
> Environment: Amazon Linux
> Reporter: Senthilvel Rangaswamy
> Attachments: cassandra-mck.log.bz2, err.txt
>
>
> Seeing errors like these:
> 2012-07-06_07:00:27.22662 ERROR 07:00:27,226 invalid counter shard detected;
> (17bfd850-ac52-11e1-0000-6ecd0b5b61e7, 1, 13) and
> (17bfd850-ac52-11e1-0000-6ecd0b5b61e7, 1, 1) differ only in count; will pick
> highest to self-heal; this indicates a bug or corruption generated a bad
> counter shard
> What does it mean ?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
