[
https://issues.apache.org/jira/browse/CASSANDRA-16451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17313585#comment-17313585
]
maxwellguo commented on CASSANDRA-16451:
----------------------------------------
[~clohfink]
"Great idea! should be sure to add a throttle in the deletion to prevent
trashing drives", I remember that jeff have done some similar work , we may use
the code or the delete function .
besides I think the ttl for snapshot may be usefull for the table that be
truncate when the auto_snapshot is set true . for the snapshot we make
mannually , we also know that the snapshot is exists, so we can clean it
mannually. so the ttl for this kind of snapshot may not be of some meaning.
But for the truncate table's snapshot we may need a recycle bin, and the
Recycle bin may need a ttl . In this way ,I think snapshot ttl is of much
meanning.
> 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]
