[ 
https://issues.apache.org/jira/browse/CASSANDRA-16789?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17401570#comment-17401570
 ] 

Abuli Palagashvili commented on CASSANDRA-16789:
------------------------------------------------

Patch is almost ready.We've added new entities {{TableSnapshot}} and 
{{SnapshotManifest}}.Now all information about snapshots (including creation 
and expiration times) is stored into this objects.We've also added 
{{SnapshotManager}} class for tracking, indexing and removing of expiring 
snapshots.We made it a part of {{StorageService}}.Cleanup process is 
implemented as regularly run task.Cassandra operator can specify period between 
launches.We've also added columns {{CreatedAt}} and {{ExpiresAt}} columns to 
{{listsnapshots}} nodetool command output.

> Add TTL support to nodetool snapshots
> -------------------------------------
>
>                 Key: CASSANDRA-16789
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-16789
>             Project: Cassandra
>          Issue Type: Sub-task
>          Components: Tool/nodetool
>            Reporter: Paulo Motta
>            Assignee: Abuli Palagashvili
>            Priority: Normal
>
> Add new parameter {{--ttl}} to {{nodetool snapshot}} command. This parameter 
> can be specified in human readable duration (ie. 30mins, 1h, 300d) and should 
> not be lower than 1 minute.
> The expiration date should be added to the snapshot manifest in ISO format.
> A periodic thread should efficiently scan snapshots and automatically clear 
> those past expiration date. The periodicity of the scan thread should be 1 
> minute by default but be overridable via a system property.
> The command {{nodetool listsnapshots}} should display the expiration date 
> when the snapshot contains a TTL.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to