You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Oleg Kibirev (JIRA)" <ji...@apache.org> on 2012/11/12 23:31:12 UTC
[jira] [Created] (CASSANDRA-4951) Leveled compaction manifest
sometimes references nonexistent sstables in a snapshot
Oleg Kibirev created CASSANDRA-4951:
---------------------------------------
Summary: 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
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
[jira] [Assigned] (CASSANDRA-4951) Leveled compaction manifest
sometimes references nonexistent sstables in a snapshot
Posted by "Brandon Williams (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-4951?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brandon Williams reassigned CASSANDRA-4951:
-------------------------------------------
Assignee: Yuki Morishita
> 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