Return-Path: X-Original-To: apmail-cassandra-commits-archive@www.apache.org Delivered-To: apmail-cassandra-commits-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id C89921899B for ; Tue, 26 May 2015 19:01:39 +0000 (UTC) Received: (qmail 12799 invoked by uid 500); 26 May 2015 19:01:17 -0000 Delivered-To: apmail-cassandra-commits-archive@cassandra.apache.org Received: (qmail 12764 invoked by uid 500); 26 May 2015 19:01:17 -0000 Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cassandra.apache.org Delivered-To: mailing list commits@cassandra.apache.org Received: (qmail 12753 invoked by uid 99); 26 May 2015 19:01:17 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 26 May 2015 19:01:17 +0000 Date: Tue, 26 May 2015 19:01:17 +0000 (UTC) From: "Jonathan Ellis (JIRA)" To: commits@cassandra.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (CASSANDRA-9484) Inconsistent select count MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ 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)