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

Benedict commented on CASSANDRA-7232:
-------------------------------------

Missed this due to status != Patch Available

I'm not keen on passing properties around using System.get/setProperty after 
system startup. We should modify CommitLogReplay so we can instantiate it with 
a specific PIT, and construct one specifically for this out-of-band restore. 
Also the comment is inaccurate, stating it is the point to restore _from_, not 
_to_. However it would be useful to be able to provide both, as presumably the 
commitlog archive directory will have more logs than needed.

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

Reply via email to