[
https://issues.apache.org/jira/browse/CASSANDRA-3318?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Ellis updated CASSANDRA-3318:
--------------------------------------
Affects Version/s: (was: 0.7.3)
1.0.0
Fix Version/s: (was: 0.8.8)
I'm only going to commit this to 1.0 after all, because before that our
PhantomReference-based deleting is very unlikely to run into this problem, so
I'm going to let the stable releases stay stable.
> Unable to delete after running scrub
> ------------------------------------
>
> Key: CASSANDRA-3318
> URL: https://issues.apache.org/jira/browse/CASSANDRA-3318
> Project: Cassandra
> Issue Type: Bug
> Components: Core
> Affects Versions: 1.0.0
> Reporter: Radim Kolar
> Assignee: Jonathan Ellis
> Priority: Minor
> Fix For: 1.0.0
>
> Attachments: 3318.txt
>
>
> Another problem with sstable deletions on 1.0. Running scrub produces lot of
> unable to delete messages on windows.
> ERROR 16:16:37,562 Unable to delete
> \var\lib\cassandra\data\test\sipdb-h-711-Dat
> a.db (it will be removed on server restart; we'll also retry after GC)
> INFO 16:16:37,577 Scrub of
> SSTableReader(path='\var\lib\cassandra\data\test\sip
> db-h-711-Data.db') complete: 48396 rows in new sstable and 0 empty
> (tombstoned)
> rows dropped
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
