You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@cassandra.apache.org by "Philip Thompson (JIRA)" <ji...@apache.org> on 2015/05/11 20:23:00 UTC

[jira] [Updated] (CASSANDRA-9346) Expand upgrade testing for commitlog changes

     [ https://issues.apache.org/jira/browse/CASSANDRA-9346?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Philip Thompson updated CASSANDRA-9346:
---------------------------------------
    Summary: Expand upgrade testing for commitlog changes  (was: Verify existing upgrade tests cover 2.1 -> 2.2 commitlog changes,)

> Expand upgrade testing for commitlog changes
> --------------------------------------------
>
>                 Key: CASSANDRA-9346
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-9346
>             Project: Cassandra
>          Issue Type: Test
>          Components: Tests
>            Reporter: Philip Thompson
>            Assignee: Branimir Lambov
>
> It seems that the current upgrade dtests always flush/drain a node before upgrading it, meaning we have no coverage of reading the commitlog files from a previous version.
> We should add (unless they exist somewhere I am not aware of ) a suite of tests that specifically target upgrading with a significant amount of data left in the commitlog files, that needs to be read by the upgraded node.



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