cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Russ Hatch (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-11195) paging may returns incomplete results on small page size
Date Fri, 18 Mar 2016 15:39:33 GMT


Russ Hatch commented on CASSANDRA-11195:

Local repro notes:
grab this dtest branch:
pip install ipdb
run the test in a loop until it fails and you can interactively debug, this might take a while...
for i in $(seq 1 100); do echo $i; UPGRADE_TEST_RUN=true nosetests upgrade_tests/;

> paging may returns incomplete results on small page size
> --------------------------------------------------------
>                 Key: CASSANDRA-11195
>                 URL:
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Jim Witschey
>            Assignee: Russ Hatch
>              Labels: dtest
>         Attachments: node1.log, node1_debug.log, node2.log, node2_debug.log
> This was found through a flapping test, and running that test is still the easiest way
to repro the issue. On CI we're seeing a 40-50% failure rate, but locally this test fails
much less frequently.
> If I attach a python debugger and re-query the "bad" query, it continues to return incomplete
data indefinitely. If I go directly to cqlsh I can see all rows just fine.
> On some upgrade paths, {{static_columns_paging_test}} is flapping:
> The failures indicate there is missing data. I have not reproduced the failure locally.
I've only seen the failures on 2-node clusters with RF=1, not on the 3-node runs with RF=3.

This message was sent by Atlassian JIRA

View raw message