cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Boxenhorn (JIRA)" <j...@apache.org>
Subject [jira] Commented: (CASSANDRA-2264) Restore From Snapshot eg: nodetool restore [filename] | ([keyspace] [columnfamily])
Date Fri, 04 Mar 2011 12:05:38 GMT

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

David Boxenhorn commented on CASSANDRA-2264:
--------------------------------------------

"Why do we need to store additional metadata?"

Is this meta-data already available somewhere? 

If I have a bad SSTable I want to know how it got bad. (I want to know that real bad.) I want
as much information as possible - you never know what piece of information will lead you to
the bug. In particular, knowing which process created it could point me in the right direction,
even in the case that it's a hardware bug.

May I suggest a human-readable -Stat table (perhaps, name-value pairs) alongside every -Data
table, with as much information as possible in it, so that no special tools would be needed
for forensics? Among the information in the -Stat table would be the SSTable's ancestors (if
any) and which process created it. 

I am speaking from the point of view of a somewhat, but not completely, naive user. Solutions
have to be available to people like me. I have a machine which used to be a bad node that
I swapped out of the cluster. The data is still there. What kinds of tools do I need to enable
me to do forensics on that detached node? If not the above, then what? That's what I want.


> Restore From Snapshot eg: nodetool restore  [filename] | ([keyspace] [columnfamily])

> -------------------------------------------------------------------------------------
>
>                 Key: CASSANDRA-2264
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-2264
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Core
>    Affects Versions: 0.7.2
>            Reporter: Benjamin Coverston
>
> Store additional metadata in the SSTable including:
> generated_by: (From memtable, compaction, or cleanup)
> ancestors: A list of SSTableNames|MD5sum
> When executed it will copy the ancestors from the snapshot directory to the data directory.
> If given Keyspace and ColumnFamily arguments it will attempt to restore all SSTables
in the Keyspace/Columnfamily on that node.

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message