[
https://issues.apache.org/jira/browse/CASSANDRA-11195?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15483535#comment-15483535
]
Benjamin Lerer edited comment on CASSANDRA-11195 at 9/12/16 8:53 AM:
---------------------------------------------------------------------
Committed into 3.0 at 932f3ebbe9005582a4e253c84f4f20aef3a0abac and into 3.9 at
c11c7d73d086f89521805ce7cc1907d5788ab969 and merged both branches into trunk
was (Author: blerer):
Committed into 3.0 at 932f3ebbe9005582a4e253c84f4f20aef3a0abac and into 3.9 at
c11c7d73d086f89521805ce7cc1907d5788ab969 an merged both branches into trunk
> 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
> Fix For: 3.0.9, 3.9
>
> 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)
