cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Adam Holmberg (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CASSANDRA-10007) Repeated rows in paged result
Date Thu, 06 Aug 2015 18:38:04 GMT

     [ https://issues.apache.org/jira/browse/CASSANDRA-10007?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Adam Holmberg updated CASSANDRA-10007:
--------------------------------------
    Description: 
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.



  was:
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.

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.




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

Mime
View raw message