Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Wed, 19 Aug 2015 17:29:46 +0000 (UTC)
From: "Steve Wang (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12852660.1438885736000.109291.1440005386280@Atlassian.JIRA>
In-Reply-To: <JIRA.12852660.1438885736000@Atlassian.JIRA>
References: <JIRA.12852660.1438885736000@Atlassian.JIRA>
 <JIRA.12852660.1438885736526@arcas>
Subject: [jira] [Commented] (CASSANDRA-10007) Repeated rows in paged result
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Steve Wang commented on CASSANDRA-10007:
----------------------------------------

Hi Benjamin! Yes, I'm still able to reproduce this error. What I do is start a 3 node cluster in CCM and then run the paging-test.py script that Adam attached in this ticket. The first two values are as expected, but the next few values, which should be 100, oscillate between 104 and 103.

> Repeated rows in paged result
> -----------------------------
>
>                 Key: CASSANDRA-10007
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-10007
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>            Reporter: Adam Holmberg
>            Assignee: Benjamin Lerer
>              Labels: client-impacting
>             Fix For: 3.x
>
>         Attachments: paging-test.py
>
>
> We noticed an anomaly in paged results while testing against 3.0.0-alpha1. It seems that unbounded selects can return rows repeated at page boundaries. Furthermore, the number of repeated rows seems to dither in count across consecutive runs of the same query.
> Does not reproduce on 2.2.0 and earlier.
> I also noted that this behavior only manifests on multi-node clusters.
> The attached script shows this behavior when run against 3.0.0-alpha1.


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