[
https://issues.apache.org/jira/browse/CASSANDRA-10907?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15066956#comment-15066956
]
Anubhav Kale commented on CASSANDRA-10907:
------------------------------------------
I agree that what is backed up will be undefined. In my opinion, the trap is
very clear here so I don't think it can be misused. IMHO, the other nodetool
commands have such traps as well so this is no different (e.g. why does scrub
have an option to not snapshot ?).
That said, if you feel strongly against this, I understand and we can kill this
(I can always make a local patch).
BTW I can't use incremental backups, because I do not want to ship SS Table
files that would have been removed as part of compaction. When compaction kicks
in and deletes some files, it won't remove them from backups (which makes sense
else it won't be incremental). So, at the time of recovery we are moving too
many files back thus increasing the downtime of Apps. If I am not understanding
something correctly here, please let me know !
> 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)
