[
https://issues.apache.org/jira/browse/CASSANDRA-8377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15273135#comment-15273135
]
Chris Lohfink commented on CASSANDRA-8377:
------------------------------------------
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)
