[jira] [Updated] (CASSANDRA-6986) snapshot fails with SSTable not found if table has already been restored
[ https://issues.apache.org/jira/browse/CASSANDRA-6986?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alan Boudreault updated CASSANDRA-6986: --- Attachment: test.sh 6986.tar.gz [~slowenthal] I am trying to reproduce this issue without luck at the moment. Do you have more detail on the environment I should create to get that error? I've attached the files I'm using for my test case, maybe you can take a look at the the !test.sh! file and see if my steps are ok. Thanks! > 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)
[jira] [Updated] (CASSANDRA-6986) snapshot fails with SSTable not found if table has already been restored
[ https://issues.apache.org/jira/browse/CASSANDRA-6986?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alan Boudreault updated CASSANDRA-6986: --- Tester: Alan Boudreault > 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 > > 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)
[jira] [Updated] (CASSANDRA-6986) snapshot fails with SSTable not found if table has already been restored
[ https://issues.apache.org/jira/browse/CASSANDRA-6986?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Ellis updated CASSANDRA-6986: -- Component/s: (was: Core) Tools Priority: Minor (was: Major) Assignee: Ryan McGuire (was: Marcus Eriksson) Ryan, can your team see if this reproduces in 2.1? > 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 > > 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)
[jira] [Updated] (CASSANDRA-6986) snapshot fails with SSTable not found if table has already been restored
[ https://issues.apache.org/jira/browse/CASSANDRA-6986?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Ellis updated CASSANDRA-6986: -- Assignee: Marcus Eriksson (was: Yuki Morishita) > 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: Marcus Eriksson > > 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)
