cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Ellis (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-9484) Inconsistent select count
Date Tue, 26 May 2015 19:01:17 GMT

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

Jonathan Ellis commented on CASSANDRA-9484:
-------------------------------------------

Is this a vnode-enabled test?  If it is separate from CASSANDRA-8940 then it could be worth
bisecting to see where the trunk regression is from, but if it wasn't working on 2.1 either
before 8940 that's probably not very useful.

> 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)

Mime
View raw message