[
https://issues.apache.org/jira/browse/CASSANDRA-7232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14057261#comment-14057261
]
Benedict commented on CASSANDRA-7232:
-------------------------------------
Really we need to be able to specify the location of any archived commit logs
and the point-in-time we want to recover to. As it stands it's just going to
replay what happens to still be in its commit log and whatever restore command
the node was started up with (probably none, but maybe one, but possibly the
wrong one)
> Enable live replay of commit logs
> ---------------------------------
>
> Key: CASSANDRA-7232
> URL: https://issues.apache.org/jira/browse/CASSANDRA-7232
> Project: Cassandra
> Issue Type: Improvement
> Components: Tools
> Reporter: Patrick McFadin
> Assignee: Lyuben Todorov
> Priority: Minor
> Fix For: 2.0.10
>
> Attachments:
> 0001-Expose-CommitLog-recover-to-JMX-add-nodetool-cmd-for.patch,
> 0001-TRUNK-JMX-and-nodetool-cmd-for-commitlog-replay.patch
>
>
> Replaying commit logs takes a restart but restoring sstables can be an online
> operation with refresh. In order to restore a point-in-time without a
> restart, the node needs to live replay the commit logs from JMX and a
> nodetool command.
> nodetool refreshcommitlogs <keyspace> <table>
--
This message was sent by Atlassian JIRA
(v6.2#6252)
