cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Benedict (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-7232) Enable live replay of commit logs
Date Tue, 15 Jul 2014 11:34:05 GMT


Benedict commented on CASSANDRA-7232:

That looks a bit error prone: it should at least take a list of directories. However I'm a
little uncomfortable passing node-local paths remotely over nodetool in general, especially
when we have very little to help ensure we got it right (we should at least print a list of
restored log files when done). In general, I think it would be safer to specify the commit
log restore/archive location at startup, but not automatically restore them if specified (have
a separate option); then the nodetool command always uses that path, and only accepts a point-in-time

This is ripe for some bikeshedding, though. [~jbellis] [~thobbs] [~pmcfadin]?

> Enable live replay of commit logs
> ---------------------------------
>                 Key: CASSANDRA-7232
>                 URL:
>             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,
> 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

View raw message