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-8377) Coordinated Commitlog Replay
Date Thu, 05 May 2016 17:08:13 GMT

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

Nick Bailey commented on CASSANDRA-8377:
----------------------------------------

Not sure if Chris has had time to do anything with this lately but I don't think we should
close this ticket if thats what you mean.

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

Mime
View raw message