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 (JIRA)" <ji...@apache.org> on 2014/02/24 15:49:20 UTC

[jira] [Comment Edited] (CASSANDRA-6326) Snapshot should create manifest file

    [ https://issues.apache.org/jira/browse/CASSANDRA-6326?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13910361#comment-13910361 ] 

Jonathan Ellis edited comment on CASSANDRA-6326 at 2/24/14 2:47 PM:
--------------------------------------------------------------------

I thought we're talking about the manifest file used by LCS.  If we're not, any snapshot-processing tools you create in-house are welcome to throw around a list of files involved but I'm not sure that belongs in the C* server.


was (Author: jbellis):
I thought we're talking about the manifest file used by LCS.

> Snapshot should create manifest file 
> -------------------------------------
>
>                 Key: CASSANDRA-6326
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-6326
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Core
>            Reporter: sankalp kohli
>            Assignee: sankalp kohli
>            Priority: Minor
>
> We should create a manifest file as part of the snapshot which should contain all the stables included in the snapshot. 
> This will be very important for systems consuming this snapshot as they can validate the fact that they got the complete snapshot. 
> If Cassandra crashes mid way creating a snapshot, I think it will create an incomplete snapshot. 



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)