cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stefania (JIRA)" <j...@apache.org>
Subject [jira] [Created] (CASSANDRA-12565) Node may not start when upgrading from 2.2 to 3.0 if drain is not run
Date Tue, 30 Aug 2016 08:46:20 GMT
Stefania created CASSANDRA-12565:
------------------------------------

             Summary: 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


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

Mime
View raw message