[ https://issues.apache.org/jira/browse/CASSANDRA-11195?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Russ Hatch updated CASSANDRA-11195: ----------------------------------- Description: 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: http://cassci.datastax.com/job/upgrade_tests-all/9/testReport/upgrade_tests.paging_test/TestPagingDataNodes2RF1_2_2_HEAD_UpTo_Trunk/static_columns_paging_test/history/ http://cassci.datastax.com/job/upgrade_tests-all/8/testReport/upgrade_tests.paging_test/TestPagingDataNodes2RF1_2_2_UpTo_Trunk/static_columns_paging_test/history/ http://cassci.datastax.com/job/upgrade_tests-all/8/testReport/upgrade_tests.paging_test/TestPagingDataNodes2RF1_2_2_UpTo_3_3_HEAD/static_columns_paging_test/history 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. was: On some upgrade paths, {{static_columns_paging_test}} is flapping: http://cassci.datastax.com/job/upgrade_tests-all/9/testReport/upgrade_tests.paging_test/TestPagingDataNodes2RF1_2_2_HEAD_UpTo_Trunk/static_columns_paging_test/history/ http://cassci.datastax.com/job/upgrade_tests-all/8/testReport/upgrade_tests.paging_test/TestPagingDataNodes2RF1_2_2_UpTo_Trunk/static_columns_paging_test/history/ http://cassci.datastax.com/job/upgrade_tests-all/8/testReport/upgrade_tests.paging_test/TestPagingDataNodes2RF1_2_2_UpTo_3_3_HEAD/static_columns_paging_test/history 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. > 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: 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: > http://cassci.datastax.com/job/upgrade_tests-all/9/testReport/upgrade_tests.paging_test/TestPagingDataNodes2RF1_2_2_HEAD_UpTo_Trunk/static_columns_paging_test/history/ > http://cassci.datastax.com/job/upgrade_tests-all/8/testReport/upgrade_tests.paging_test/TestPagingDataNodes2RF1_2_2_UpTo_Trunk/static_columns_paging_test/history/ > http://cassci.datastax.com/job/upgrade_tests-all/8/testReport/upgrade_tests.paging_test/TestPagingDataNodes2RF1_2_2_UpTo_3_3_HEAD/static_columns_paging_test/history > 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 (v6.3.4#6332)