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 Mon, 13 Apr 2015 15:19:12 GMT

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

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

Cancelled patch and targeted 3.0. I'll remove the soft-linking; I agree that it doesn't make
a lot of sense in retrospect.

> 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: 3.0
>
>
> 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