[
https://issues.apache.org/jira/browse/CASSANDRA-16451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17305524#comment-17305524
]
Abuli Palagashvili commented on CASSANDRA-16451:
------------------------------------------------
[~paulo] I have played a bit with CCM and manually-made snapshots.As I
understand right now, after snapshot creation it is not managed by
cassandra.Also, each snapshot has it's own manifest.json file with metadata.So,
we can write expiration timestamp to each such file and make cassandra
regularly scanning folders with keyspaces/column families and
detecting/removing outdated snapshots.Correct me if I'm wrong, please.
> Add ability to ttl snapshots
> ----------------------------
>
> Key: CASSANDRA-16451
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16451
> Project: Cassandra
> Issue Type: Improvement
> Components: Tool/nodetool
> Reporter: Paulo Motta
> Priority: Normal
> Labels: gsoc2021, mentor
>
> It should be possible to add a TTL to snapshots, after which it automatically
> cleans itself up.
> This will be useful together with the {{auto_snapshot}} option, where you
> want to keep an emergency snapshot in case of accidental drop or truncation
> but automatically remove it after a specified period when it's no longer
> useful. So in addition to allowing a user to specify a snapshot ttl on
> {{nodetool snapshot}} we should have a {{auto_snapshot_ttl}} option that
> allows a user to set a ttl for automatic snaphots on drop/truncate.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
