[jira] [Commented] (CASSANDRA-10476) Fix upgrade paging dtest failures on 2.2->3.0 path

["Benjamin Lerer (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/CASSANDRA-10476?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15037607#comment-15037607 ] 

Benjamin Lerer commented on CASSANDRA-10476:
--------------------------------------------

I had a look at the latest runs of the tests. It seems that we still have some timeouts. {{test_query_isolation}} had only 1 in 42 runs. {{test_single_partition_deletions}} is the one having the most, but it is also the test making the biggest amount of queries. Failure happen on different queries.

As it is some RF3 tests, the randomness cannot come from the way data is distributed over the nodes.

The coordinator  version does not seems to play a role as the problem occurs when the coordinator is the upgraded node as well as when it is the old node.

So far, I have never been able to reproduce the problem locally. I will try to look at the variance in response time and see if it leads me somewhere.

> Fix upgrade paging dtest failures on 2.2->3.0 path
> --------------------------------------------------
>
>                 Key: CASSANDRA-10476
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-10476
>             Project: Cassandra
>          Issue Type: Sub-task
>            Reporter: Jim Witschey
>            Assignee: Benjamin Lerer
>             Fix For: 3.0.1, 3.1
>
>
> EDIT: this list of failures is no longer current; see comments for current failures.
> The following upgrade tests for paging features fail or flap on the upgrade path from 2.2 to 3.0:
> - {{upgrade_tests/paging_test.py:TestPagingData.static_columns_paging_test}}
> - {{upgrade_tests/paging_test.py:TestPagingSize.test_undefined_page_size_default}}
> - {{upgrade_tests/paging_test.py:TestPagingSize.test_with_more_results_than_page_size}}
> - {{upgrade_tests/paging_test.py:TestPagingWithDeletions.test_failure_threshold_deletions}}
> - {{upgrade_tests/paging_test.py:TestPagingWithDeletions.test_multiple_cell_deletions}}
> - {{upgrade_tests/paging_test.py:TestPagingWithDeletions.test_single_cell_deletions}}
> - {{upgrade_tests/paging_test.py:TestPagingWithDeletions.test_single_row_deletions}}
> - {{upgrade_tests/paging_test.py:TestPagingDatasetChanges.test_cell_TTL_expiry_during_paging/}}
> I've grouped them all together because I don't know how to tell if they're related; once someone triages them, it may be appropriate to break this out into multiple tickets.
> The failures can be found here:
> http://cassci.datastax.com/view/Upgrades/job/storage_engine_upgrade_dtest-22_tarball-30_HEAD/44/testReport/upgrade_tests.paging_test/TestPagingData/static_columns_paging_test/history/
> http://cassci.datastax.com/view/Upgrades/job/storage_engine_upgrade_dtest-22_tarball-30_HEAD/44/testReport/upgrade_tests.paging_test/TestPagingSize/test_undefined_page_size_default/history/
> http://cassci.datastax.com/view/Upgrades/job/storage_engine_upgrade_dtest-22_tarball-30_HEAD/42/testReport/upgrade_tests.paging_test/TestPagingSize/test_with_more_results_than_page_size/history/
> http://cassci.datastax.com/view/Upgrades/job/storage_engine_upgrade_dtest-22_tarball-30_HEAD/44/testReport/upgrade_tests.paging_test/TestPagingWithDeletions/test_failure_threshold_deletions/history/
> http://cassci.datastax.com/view/Upgrades/job/storage_engine_upgrade_dtest-22_tarball-30_HEAD/44/testReport/upgrade_tests.paging_test/TestPagingWithDeletions/test_multiple_cell_deletions/history/
> http://cassci.datastax.com/view/Upgrades/job/storage_engine_upgrade_dtest-22_tarball-30_HEAD/44/testReport/upgrade_tests.paging_test/TestPagingWithDeletions/test_single_cell_deletions/history/
> http://cassci.datastax.com/view/Upgrades/job/storage_engine_upgrade_dtest-22_tarball-30_HEAD/44/testReport/upgrade_tests.paging_test/TestPagingWithDeletions/test_single_row_deletions/history/
> http://cassci.datastax.com/view/Upgrades/job/storage_engine_upgrade_dtest-22_tarball-30_HEAD/44/testReport/upgrade_tests.paging_test/TestPagingDatasetChanges/test_cell_TTL_expiry_during_paging/
> Once [this dtest PR|https://github.com/riptano/cassandra-dtest/pull/586] is merged, these tests should also run with this upgrade path on normal 3.0 jobs. Until then, you can run them with the following command:
> {code}
> SKIP=false CASSANDRA_VERSION=binary:2.2.0 UPGRADE_TO=git:cassandra-3.0 nosetests upgrade_tests/paging_test.py:TestPagingData.static_columns_paging_test upgrade_tests/paging_test.py:TestPagingSize.test_undefined_page_size_default upgrade_tests/paging_test.py:TestPagingSize.test_with_more_results_than_page_size upgrade_tests/paging_test.py:TestPagingWithDeletions.test_failure_threshold_deletions upgrade_tests/paging_test.py:TestPagingWithDeletions.test_multiple_cell_deletions upgrade_tests/paging_test.py:TestPagingWithDeletions.test_single_cell_deletions upgrade_tests/paging_test.py:TestPagingWithDeletions.test_single_row_deletions
> upgrade_tests/paging_test.py:TestPagingDatasetChanges.test_cell_TTL_expiry_during_paging
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)