[
https://issues.apache.org/jira/browse/CASSANDRA-8271?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14724715#comment-14724715
]
Stefania commented on CASSANDRA-8271:
-------------------------------------
CASSANDRA-7066 has replaced {{SSTableDeletingTask}} with
{{TransactionLog.SSTableTidier}}. In addition to performing the tasks of
{{SSTableDeletingTask}}, it keeps a reference to the transaction and it ensures
its log file is only removed after all sstable files are already removed.
> Remove SSTableDeletingTask
> --------------------------
>
> Key: CASSANDRA-8271
> URL: https://issues.apache.org/jira/browse/CASSANDRA-8271
> Project: Cassandra
> Issue Type: Improvement
> Reporter: Joshua McKenzie
> Assignee: Joshua McKenzie
> Priority: Minor
> Fix For: 3.x
>
>
> With CASSANDRA-4050 and CASSANDRA-6993, our out-of-order deletion problems
> w/regards to Windows are resolved and the only outstanding reason to have
> SSTableDeletingTask would be for support of non-sun VM's w/regards to mmap'ed
> files. As this is no longer a big concern in the Cassandra ecosystem
> (non-sun VM's), we should remove SSTableDeletingTask.
> The one caveat is that if we want to revisit mmap'ed I/O on Windows in the
> future we may need to re-use this type of "delayed deletion" approach due to
> Windows not allowing deletion of hard linked files w/memory-mapped segments
> in the original file, but CASSANDRA-5863 would obviate that concern.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
