[ https://issues.apache.org/jira/browse/CASSANDRA-8271?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Joshua McKenzie resolved CASSANDRA-8271. ---------------------------------------- Resolution: Later Fix Version/s: (was: 3.x) W/the changes from CASSANDRA-7066, CASSANDRA-9658, and finally CASSANDRA-10222, removing the various recurring deletion tasks isn't going to be viable until CASSANDRA-5863 (or some other buffered vs. mmap parity) comes through. Closing as later pending those efforts. > 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 > > 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)