cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Joshua McKenzie (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-7555) Support copy and link for commitlog archiving without forking the jvm
Date Thu, 29 Jan 2015 19:07:36 GMT

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

Joshua McKenzie commented on CASSANDRA-7555:
--------------------------------------------

Feature branch [available here|https://github.com/josh-mckenzie/cassandra/compare/7555]. 
Added some new Windows-specific handling for createDirectory in FileUtils, a copyFile method
I pulled from commons-io, and some unit tests.  The only change that escapes the scope of
the new additions is that I switched to using FileUtils.createDirectory in the constructor
for the CommitLogArchiver so errors creating the directories will bubble up as FSWriteErrors
now instead of RuntimeErrors.  I believe that will be acceptable but figured I'd point it
out.

> Support copy and link for commitlog archiving without forking the jvm
> ---------------------------------------------------------------------
>
>                 Key: CASSANDRA-7555
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-7555
>             Project: Cassandra
>          Issue Type: Improvement
>            Reporter: Nick Bailey
>            Assignee: Joshua McKenzie
>            Priority: Minor
>             Fix For: 2.1.3
>
>
> Right now for commitlog archiving the user specifies a command to run and c* forks the
jvm to run that command. The most common operations will be either copy or link (hard or soft).
Since we can do all of these operations without forking the jvm, which is very expensive,
we should have special cases for those.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message