You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Steven Lowenthal (JIRA)" <ji...@apache.org> on 2014/04/06 02:28:14 UTC

[jira] [Created] (CASSANDRA-6986) snapshot fails with SSTable not found if table has already been restored

Steven Lowenthal created CASSANDRA-6986:
-------------------------------------------

             Summary: snapshot fails with SSTable not found if table has already been restored
                 Key: CASSANDRA-6986
                 URL: https://issues.apache.org/jira/browse/CASSANDRA-6986
             Project: Cassandra
          Issue Type: Bug
          Components: Core
         Environment: C* 2.0.6
            Reporter: Steven Lowenthal


I seem to be running into a weird restore issue.  I load a database with sstableloader, and then take a snapshot of the keyspace.  I then truncate the tables in the keyspace, replace the sstables from the snapshot, and refresh everything.  It seems to work fine.  Of course the sstables get renumbered.  I then try to create a new backup of the keyspace, and this happens on one of the tables on one of the nodes.  (and the sstable has been renumbered): Exception in thread "main" java.lang.RuntimeException: Tried to hard link to file that does not exist /raid0/cassandra/data/stock/trades/stock-trades-jb-18-Data.db



--
This message was sent by Atlassian JIRA
(v6.2#6252)