[
https://issues.apache.org/jira/browse/CASSANDRA-7555?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15101765#comment-15101765
]
Joshua McKenzie commented on CASSANDRA-7555:
--------------------------------------------
I think "put on a back-burner" is a more political way to phrase it. :)
Given the limited scope of use-cases this affects and the uncategorized (at
least thus far) performance differential of a native vs. forked solution, this
hasn't been high on my priority list. I can adjust if there's a strong case to
be made otherwise.
> 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
> Components: Local Write-Read Paths
> Reporter: Nick Bailey
> Assignee: Joshua McKenzie
> Priority: Minor
> Fix For: 3.x
>
>
> 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)
