[
https://issues.apache.org/jira/browse/CASSANDRA-10907?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15066826#comment-15066826
]
Nick Bailey commented on CASSANDRA-10907:
-----------------------------------------
My only objection is that the behavior of what information is actually backed
up is basically undefined. It's possibly it's useful in some very specific use
cases but it also introduces potential traps when used incorrectly.
It sounds to me like you should be using incremental backups. When that is
enabled a hardlink is created every time a memtable is flushed or an sstable
streamed. You can then just watch that directory and ship the sstables off node
on demand as they are created.
> Nodetool snapshot should provide an option to skip flushing
> -----------------------------------------------------------
>
> Key: CASSANDRA-10907
> URL: https://issues.apache.org/jira/browse/CASSANDRA-10907
> Project: Cassandra
> Issue Type: Improvement
> Components: Configuration
> Environment: PROD
> Reporter: Anubhav Kale
> Priority: Minor
> Labels: lhf
>
> For some practical scenarios, it doesn't matter if the data is flushed to
> disk before taking a snapshot. However, it's better to save some flushing
> time to make snapshot process quick.
> As such, it will be a good idea to provide this option to snapshot command.
> The wiring from nodetool to MBean to VerbHandler should be easy.
> I can provide a patch if this makes sense.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
