[
https://issues.apache.org/jira/browse/CASSANDRA-7232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14061934#comment-14061934
]
Lyuben Todorov commented on CASSANDRA-7232:
-------------------------------------------
So we want the nodetool command to accept a list of commit logs and the
point-in-time to recover to? Something along the lines of: nodetool
replaycommitlogs ks cf point-in-time list-of-commitlogs
eg:
{{nodetool replaycommitogs demodb usertable -point-in-time 1404777106690
C*_DIR/data/commitlogs/CommitLog-4-1404777106690.log
C*_DIR/data/commitlogs/CommitLog-4-1404777106696.log
C*_DIR/data/commitlogs/CommitLog-4-1404777106698.log}}
> 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)
