[
https://issues.apache.org/jira/browse/CASSANDRA-8377?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
C. Scott Andreas updated CASSANDRA-8377:
----------------------------------------
Component/s: Core
> Coordinated Commitlog Replay
> ----------------------------
>
> Key: CASSANDRA-8377
> URL: https://issues.apache.org/jira/browse/CASSANDRA-8377
> Project: Cassandra
> Issue Type: New Feature
> Components: Core
> Reporter: Nick Bailey
> Assignee: Chris Lohfink
> Priority: Major
> Fix For: 4.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
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
