[
https://issues.apache.org/jira/browse/CASSANDRA-11195?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15451802#comment-15451802
]
Benjamin Lerer commented on CASSANDRA-11195:
--------------------------------------------
I am not sure why but I could not reproduce the problem again in a 100 runs. It
is quite frustrating.
[~rhatch] I will need your help. I have pushed a modified version of 3.9
[here|https://github.com/blerer/cassandra/tree/11195-3.9]. It add some logging
statement to allow me to understand the problem (as it seems that the problem
happen when the coordinator is the 3.9 branch).
Could you run my [DTest
branch|https://github.com/blerer/cassandra-dtest/tree/11195] with that modified
version in your environment. I would need the log files of the failing run.
> 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)
