[
https://issues.apache.org/jira/browse/CASSANDRA-5842?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Ellis resolved CASSANDRA-5842.
---------------------------------------
Resolution: Invalid
CASSANDRA-5843 is the real problem. Cassandra *does* ignore sstables it
couldn't delete, but if we have two SSTR open for it and only try to delete
through one of them, the other has no way to know.
> Cassandra should ignore sstables which it could not delete.
> ------------------------------------------------------------
>
> Key: CASSANDRA-5842
> URL: https://issues.apache.org/jira/browse/CASSANDRA-5842
> Project: Cassandra
> Issue Type: Bug
> Components: Core
> Affects Versions: 1.1.12
> Reporter: sankalp kohli
> Priority: Minor
>
> CUrrently if Cassandra could not delete an sstable, it keeps a tab of it. It
> is even eligible for compaction.
> So if file system gives an error during delete, and it actually deletes the
> file, Cassandra will think the file is there.
> It will then try to read that sstable as part of the compaction and also read
> traffic.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
