You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Jonathan Ellis (Created) (JIRA)" <ji...@apache.org> on 2012/02/28 05:46:48 UTC
[jira] [Created] (CASSANDRA-3968) LoadNewSSTables can conflict with
old incremental backups
LoadNewSSTables can conflict with old incremental backups
---------------------------------------------------------
Key: CASSANDRA-3968
URL: https://issues.apache.org/jira/browse/CASSANDRA-3968
Project: Cassandra
Issue Type: Bug
Reporter: Jonathan Ellis
Priority: Minor
Fix For: 1.1.0
If we load a new sstable from the filesystem with a generation in our "past", the incremental backup hard link may conflict with an existing one.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CASSANDRA-3968) LoadNewSSTables can conflict
with old incremental backups
Posted by "Jonathan Ellis (Resolved) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-3968?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jonathan Ellis resolved CASSANDRA-3968.
---------------------------------------
Resolution: Duplicate
Fix Version/s: (was: 1.1.0)
done in CASSANDRA-3967
> LoadNewSSTables can conflict with old incremental backups
> ---------------------------------------------------------
>
> Key: CASSANDRA-3968
> URL: https://issues.apache.org/jira/browse/CASSANDRA-3968
> Project: Cassandra
> Issue Type: Bug
> Reporter: Jonathan Ellis
> Priority: Minor
>
> If we load a new sstable from the filesystem with a generation in our "past", the incremental backup hard link may conflict with an existing one.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CASSANDRA-3968) LoadNewSSTables can conflict
with old incremental backups
Posted by "Jonathan Ellis (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-3968?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13217892#comment-13217892 ]
Jonathan Ellis commented on CASSANDRA-3968:
-------------------------------------------
As noted in CASSANDRA-3735, one solution would be to rename sstables as they are loaded, with "current" generations.
CASSANDRA-3794 offers another, more invasive solution.
> LoadNewSSTables can conflict with old incremental backups
> ---------------------------------------------------------
>
> Key: CASSANDRA-3968
> URL: https://issues.apache.org/jira/browse/CASSANDRA-3968
> Project: Cassandra
> Issue Type: Bug
> Reporter: Jonathan Ellis
> Priority: Minor
> Fix For: 1.1.0
>
>
> If we load a new sstable from the filesystem with a generation in our "past", the incremental backup hard link may conflict with an existing one.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira