[
https://issues.apache.org/jira/browse/CASSANDRA-11195?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15226679#comment-15226679
]
Russ Hatch commented on CASSANDRA-11195:
----------------------------------------
[~blerer] Yeah, I'm running that test in a loop repeatedly until it repros. I
takes some time, and iterations to occur. I'm using a python debugger just so I
can halt things and have a look around when the bug repros. Comment above has
details on that here:
https://issues.apache.org/jira/browse/CASSANDRA-11195?focusedCommentId=15201650&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15201650
> paging may returns incomplete results on small page size
> --------------------------------------------------------
>
> Key: CASSANDRA-11195
> URL: https://issues.apache.org/jira/browse/CASSANDRA-11195
> Project: Cassandra
> Issue Type: Bug
> Reporter: Jim Witschey
> Assignee: Benjamin Lerer
> Labels: dtest
> Attachments: allfiles.tar.gz, 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.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
