cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Ellis (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (CASSANDRA-4951) Leveled compaction manifest sometimes references nonexistent sstables in a snapshot
Date Fri, 15 Feb 2013 05:19:13 GMT

     [ https://issues.apache.org/jira/browse/CASSANDRA-4951?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Jonathan Ellis resolved CASSANDRA-4951.
---------------------------------------

    Resolution: Duplicate

Addressed by CASSANDRA-4872
                
> Leveled compaction manifest sometimes references nonexistent sstables in a snapshot
> -----------------------------------------------------------------------------------
>
>                 Key: CASSANDRA-4951
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-4951
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 1.1.4
>            Reporter: Oleg Kibirev
>            Assignee: Yuki Morishita
>
> After nodetool snapshot on a node under load, we sometimes see sstables not referenced
in the leveled compaction json manifest, or sstables in the manifest which are not found on
disk. There are two concerns with this:
> 1. What would happened to leveled compaction and to reads if the snapshot is restored
with missing or extra sstables?
> 2. Is this a sign of a snapshot not having a complete copy of the data?
> To support automated restore, manifest and/or a list of links should be made correct
at snapshot time.  

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message