[jira] [Commented] (CASSANDRA-8752) invalid counter shard detected in Version 2.1.2

["Aleksey Yeschenko (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/CASSANDRA-8752?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14309040#comment-14309040 ] 

Aleksey Yeschenko commented on CASSANDRA-8752:
----------------------------------------------

It did solve it, yes (although you'll still potentially see if if you lose an sstable, for example, which is why that warning exists in code in the first place).

You'll also see it if the read-before-write to update the counter returned nothing. So it could be one of our 2.1 sstable related issues.

I suggest you try it again with Cassandra 2.1.3 once it's released (soon), or build from cassandra-2.1 branch directly, and see if you can reproduce it.

> invalid counter shard detected in Version 2.1.2
> -----------------------------------------------
>
>                 Key: CASSANDRA-8752
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-8752
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>         Environment: SUSE11 SP1, Cassandra 2.1.2, java version "1.7.0_55".
> 4 node cluster, vnode = 1, replication = 2
>            Reporter: Kevin Ye
>            Assignee: Aleksey Yeschenko
>
> I was doing counter test (first +100 several times, then -33) on a 4 nodes cluster while below log appear at 2 nodes.There is no concurrent access to same counter.
> WARN  [CompactionExecutor:757] 2015-02-02 13:02:33,375 CounterContext.java:431 - invalid global counter shard detected; (9cca9262-934a-4275-963b-66802471b0c2, 1, -33) and (9cca9262-934a-4275-963b-66802471b0c2, 1, 100) differ only in count; will pick highest to self-heal on compaction
> Anyone has encounter this problem? I thought Cassandra 2.1.2 had solved this counter problem, but it appeared.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)