[ 
https://issues.apache.org/jira/browse/CASSANDRA-4050?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13935316#comment-13935316
 ] 

Joshua McKenzie edited comment on CASSANDRA-4050 at 3/14/14 6:35 PM:
---------------------------------------------------------------------

I did some testing to confirm - nio.2 resolves both deleting hard-links and 
deleting of files with other handles currently open on Windows.  It should be 
straightforward to convert to a FileChannel and ByteBuffer in RAR and wrap the 
FileDataInput interface over to the ByteBuffer's.


was (Author: joshuamckenzie):
I did some testing to confirm - nio.2 resolves both deleting hard-links and 
deleting of files with other handles currently open on Windows.  It should be 
straightforward to convert to a SeekableByteChannel and ByteBuffer in RAR and 
wrap the FileDataInput interface over to the ByteBuffer's.

> Unable to remove snapshot files on Windows while original sstables are live
> ---------------------------------------------------------------------------
>
>                 Key: CASSANDRA-4050
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-4050
>             Project: Cassandra
>          Issue Type: Bug
>         Environment: Windows 7
>            Reporter: Jim Newsham
>            Assignee: Joshua McKenzie
>            Priority: Minor
>
> I'm using Cassandra 1.0.8, on Windows 7.  When I take a snapshot of the 
> database, I find that I am unable to delete the snapshot directory (i.e., dir 
> named "{datadir}\{keyspacename}\snapshots\{snapshottag}") while Cassandra is 
> running:  "The action can't be completed because the folder or a file in it 
> is open in another program.  Close the folder or file and try again" [in 
> Windows Explorer].  If I terminate Cassandra, then I can delete the directory 
> with no problem.
> I expect to be able to move or delete the snapshotted files while Cassandra 
> is running, as this should not affect the runtime operation of Cassandra.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Reply via email to