You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Benjamin Lerer (JIRA)" <ji...@apache.org> on 2015/05/27 08:59:20 UTC

[jira] [Comment Edited] (CASSANDRA-9484) Inconsistent select count

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

Benjamin Lerer edited comment on CASSANDRA-9484 at 5/27/15 6:58 AM:
--------------------------------------------------------------------

I might be wrong but I do not think that this issue is the same that  CASSANDRA-8940. The delta seems to always be of +1, according to the description, which make me think more about a paging issue. 


was (Author: blerer):
I might be wrong but I do not think that this issue is the same that  CASSANDRA-8940. The delta seems to always be of +1 according to the description which make me think more about a paging issue. 

> Inconsistent select count
> -------------------------
>
>                 Key: CASSANDRA-9484
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-9484
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Philip Thompson
>            Assignee: Benjamin Lerer
>             Fix For: 3.x, 2.2.x
>
>
> I am running the dtest simultaneous_bootstrap_test located at https://github.com/riptano/cassandra-dtest/compare/cassandra-7069 and finding that at the final data verification step, the query {{SELECT COUNT (*) FROM keyspace1.standard1}} alternated between correctly returning 500,000 rows and returning 500,001 rows. Running cleanup or compaction does not affect the behavior. I have verified with sstable2json that there are exactly 500k rows on disk between the two nodes in the cluster.
> I am reproducing this on trunk currently. It is not happening on 2.1-head.



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