Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Tue, 8 Dec 2015 16:47:11 +0000 (UTC)
From: "Joshua McKenzie (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12753454.1415297871000.302891.1449593231699@Atlassian.JIRA>
In-Reply-To: <JIRA.12753454.1415297871000@Atlassian.JIRA>
References: <JIRA.12753454.1415297871000@Atlassian.JIRA>
 <JIRA.12753454.1415297871706@arcas>
Subject: [jira] [Updated] (CASSANDRA-8271) Remove SSTableDeletingTask
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/CASSANDRA-8271?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Joshua McKenzie updated CASSANDRA-8271:
---------------------------------------
    Component/s: Local Write-Read Paths

> Remove SSTableDeletingTask
> --------------------------
>
>                 Key: CASSANDRA-8271
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-8271
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Local Write-Read Paths
>            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)