[ https://issues.apache.org/jira/browse/CASSANDRA-3318?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jonathan Ellis updated CASSANDRA-3318: -------------------------------------- Attachment: 3318.txt that means it's the sstable from before scrub. patch attached to close the readers before replacing the old sstable with the new one. (the diff is intimidating but it's mostly indentation changes from combining two try/finally blocks. recommend using a "smart" diff tool like intellij's post-patch application.) > 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 > Reporter: Radim Kolar > Priority: Minor > Fix For: 0.8.8, 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