cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Marcus Eriksson (JIRA)" <>
Subject [jira] [Created] (CASSANDRA-13294) Possible data loss on upgrade 2.1 - 3.0
Date Fri, 03 Mar 2017 10:04:45 GMT
Marcus Eriksson created CASSANDRA-13294:

             Summary: Possible data loss on upgrade 2.1 - 3.0
                 Key: CASSANDRA-13294
             Project: Cassandra
          Issue Type: Bug
            Reporter: Marcus Eriksson
            Assignee: Marcus Eriksson
            Priority: Blocker
             Fix For: 3.0.x

After finishing a compaction we delete the compacted away files. This is done [here|]
which uses [this|]
to get the files - we get all files starting with {{absoluteFilePath}}. Absolute file path
is generated [here|].
For 3.0 version files the filename looks like this: {{/blabla/keyspace1/standard1-bdb031c0ff7b11e6940fdd0479dd8912/mc-1332-big}}
but for 2.1 version files, they look like this: {{/blabla/keyspace1/standard1-bdb031c0ff7b11e6940fdd0479dd8912/keyspace1-standard1-ka-2}}.

The problem is then that if we were to finish a compaction including the legacy file, we would
actually delete all legacy files having a generation starting with '2'

This message was sent by Atlassian JIRA

View raw message