[jira] [Commented] (CASSANDRA-12565) Node may not start when upgrading from 2.2 to 3.0 if drain is not run

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

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

Stefania commented on CASSANDRA-12565:
--------------------------------------

2 dtest failures but unrelated to this patch: one failure is a new test that needed a rebase whilst the other one is already happening on unpatched trunk.

Committed to 3.0 as a1d9a0295c54aa044eedef7812f8ac89cc62fb2b and merged into trunk.

> Node may not start when upgrading from 2.2 to 3.0 if drain is not run
> ---------------------------------------------------------------------
>
>                 Key: CASSANDRA-12565
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-12565
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Local Write-Read Paths
>            Reporter: Stefania
>            Assignee: Stefania
>             Fix For: 3.0.9, 3.10
>
>
> Whilst debugging CASSANDRA-12457, I noticed that if we don't stop compactions when draining the 2.2 node, then we may fail to restart the node after upgrading to 3.0.
> This is because sstable names in 2.2 have been changed from _la_ to _lb_ but [{{LEGACY_TMP_REGEX_STR}}|https://github.com/apache/cassandra/blob/trunk/src/java/org/apache/cassandra/io/sstable/Descriptor.java#L187] in Descriptor.java doe not match _lb_ sstables and therefore it won't clean or ignore temporary files.



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