Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Thu, 15 Oct 2015 10:12:15 +0000 (UTC)
From: "Stefania (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12832808.1432663487000.46665.1444903935040@Atlassian.JIRA>
In-Reply-To: <JIRA.12832808.1432663487000@Atlassian.JIRA>
References: <JIRA.12832808.1432663487000@Atlassian.JIRA>
 <JIRA.12832808.1432663487542@arcas>
Subject: [jira] [Commented] (CASSANDRA-9484) Inconsistent select count
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Stefania commented on CASSANDRA-9484:
-------------------------------------

[~philipthompson] can you see if you can still reproduce it with the 2.2 patch of 10509? 

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