[
https://issues.apache.org/jira/browse/CASSANDRA-12565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15450927#comment-15450927
]
Stefania commented on CASSANDRA-12565:
--------------------------------------
dtests did not run, some problem with github, I've relaunched them.
utests had several timeouts and one unrelated failure for 3.0, but had no
failures for trunk so we can accept these results since the only utest affected
by the regex should be SystemKeyspaceTest and it ran fine on both.
> 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.x, 3.x
>
>
> 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)
