Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Fri, 6 Nov 2015 13:07:27 +0000 (UTC)
From: "Benjamin Lerer (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12903187.1444261623000.174148.1446815247737@Atlassian.JIRA>
In-Reply-To: <JIRA.12903187.1444261623000@Atlassian.JIRA>
References: <JIRA.12903187.1444261623000@Atlassian.JIRA>
 <JIRA.12903187.1444261623705@arcas>
Subject: [jira] [Commented] (CASSANDRA-10476) Fix upgrade paging dtest
 failures on 2.2->3.0 path
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

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

I add a second look to {{upgrade_tests/paging_test.py:TestPagingDataNodes2RF1.static_columns_paging_test}}. I ran the test several time for {{3.0}} and {{2.2 HEAD}} and checked how the data was distributed on the 2 nodes. I am pretty confident that the problem is fixed.
We just need to switch the upgrade tests to {{2.2.4}} once it has been released. 

For the other tests it seems that the problem is still there.

> 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.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)