You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Stefania (JIRA)" <ji...@apache.org> on 2016/09/01 02:11:20 UTC
[jira] [Updated] (CASSANDRA-12565) Node may not start when
upgrading from 2.2 to 3.0 if drain is not run
[ https://issues.apache.org/jira/browse/CASSANDRA-12565?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Stefania updated CASSANDRA-12565:
---------------------------------
Resolution: Fixed
Fix Version/s: (was: 3.0.x)
(was: 3.x)
3.10
3.0.9
Status: Resolved (was: Patch Available)
> 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)