[
https://issues.apache.org/jira/browse/CASSANDRA-6986?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14292092#comment-14292092
]
Alan Boudreault commented on CASSANDRA-6986:
--------------------------------------------
[~slowenthal] Have you experienced this issue again? If so, any chance we can
talk together to check how to reproduce it?
> 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: Tools
> Environment: C* 2.0.6
> Reporter: Steven Lowenthal
> Assignee: Ryan McGuire
> Priority: Minor
> Attachments: 6986.tar.gz, test.sh
>
>
> 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.3.4#6332)
