[
https://issues.apache.org/jira/browse/CASSANDRA-7232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14063717#comment-14063717
]
Nick Bailey commented on CASSANDRA-7232:
----------------------------------------
My initial thought is that specifying a more dynamic location will be more
"tools friendly". A location specified on startup of the jvm will probably
created/owned by the c* process which presents potential problems for external
tools. We already see this with snapshots. Also requiring a restart of the c*
process to change that location seems pretty heavyweight.
Also, should the command accept a 'start time' as well?
> 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)
