[jira] [Comment Edited] (CASSANDRA-8377) Coordinated Commitlog Replay

["Chris Lohfink (JIRA)" <ji...@apache.org>]

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

Chris Lohfink edited comment on CASSANDRA-8377 at 5/5/16 9:37 PM:
------------------------------------------------------------------

its been awhile... out of curiosity whats thoughts of making this a new tool vs a jmx thing? like sstableloader we can have a "commitlogloader". Can isolate it a little from the server. That said tacking it on to the existing commit log replay stuff is easier, but its awkward from nodetool to send a "file", kinda has to be a path that would then have to exist on the C* node that nodetool connects to.


was (Author: cnlwsu):
its been awhile... out of curiosity whats thoughts of making this a new tool vs a jmx thing? like sstableloader we can have a "commitlogloader". Can isolate it a little from the server.

> Coordinated Commitlog Replay
> ----------------------------
>
>                 Key: CASSANDRA-8377
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-8377
>             Project: Cassandra
>          Issue Type: New Feature
>            Reporter: Nick Bailey
>            Assignee: Chris Lohfink
>             Fix For: 3.x
>
>         Attachments: CASSANDRA-8377.txt
>
>
> Commit log archiving and replay can be used to support point in time restores on a cluster. Unfortunately, at the moment that is only true when the topology of the cluster is exactly the same as when the commitlogs were archived. This is because commitlogs need to be replayed on a node that is a replica for those writes.
> To support replaying commitlogs when the topology has changed we should have a tool that replays the writes in a commitlog as if they were writes from a client and will get coordinated to the correct replicas.



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