[
https://issues.apache.org/jira/browse/CASSANDRA-9484?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Philip Thompson updated CASSANDRA-9484:
---------------------------------------
Description: 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. (was: I am running the dtest
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.)
> 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.1.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.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
