cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nick Bailey (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-7555) Support copy and link for commitlog archiving without forking the jvm
Date Wed, 04 Mar 2015 17:05:05 GMT

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

Nick Bailey commented on CASSANDRA-7555:
----------------------------------------

So it seems that C* recycles commitlog segments rather than creating new ones. So I'm not
sure either of the link options are actually viable, perhaps just the copy option.

> 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.4
>
>
> 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