[
https://issues.apache.org/jira/browse/CASSANDRA-7232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14063788#comment-14063788
]
Benedict commented on CASSANDRA-7232:
-------------------------------------
With your just filed CASSANDRA-7555, it seems even more reasonable to have that
directory predefined (although offering an override on the command line seems
appropriate).
A 'start time' makes sense, esp. with long term log retention. Though I am
slightly afraid users will misuse it and restore from too late a point.
It might be useful to start encoding in the header/tail of the CL segment the
min/max timestamp present, so they can be filtered more quickly
> 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)
