You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Jonathan Ellis (JIRA)" <ji...@apache.org> on 2015/07/01 20:00:05 UTC

[jira] [Updated] (CASSANDRA-8377) Coordinated Commitlog Replay

     [ https://issues.apache.org/jira/browse/CASSANDRA-8377?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jonathan Ellis updated CASSANDRA-8377:
--------------------------------------
    Reviewer: T Jake Luciani

[~tjake] to review

> 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)