[
https://issues.apache.org/jira/browse/CASSANDRA-7232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14087832#comment-14087832
]
Lyuben Todorov commented on CASSANDRA-7232:
-------------------------------------------
Added a nodetool command to replay archived commitlogs using the directory
setting from {{commitlog_archiving.properties}} that takes a point-in-time as a
parameter (split into two params, one is the date, the other is the time, in
the same format used in the properties file for {{restore_point_in_time}}).
Command usage example below:
{noformat}
nodetool replaycommitlogs <date> <time>
nodetool replaycommitlogs 2014:08:06 10:43:12
{noformat}
One concern with the commit is that a system setting is used in
{{SS#recoverCommitlog}} to overload the point-in-time setting in the
{{CLArchiver}} which immutable, not sure if this is the best way to go about it
but if anyone has ideas I'm very open to suggestions. [Draft branch
here|https://github.com/lyubent/cassandra/commit/ce786eea52eb3e1200a7f5cf5d429257ae13c8dd].
> 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)
