[ https://issues.apache.org/jira/browse/HBASE-22648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Viraj Jasani updated HBASE-22648: --------------------------------- Attachment: HBASE-22648-master-v2.patch > Snapshot TTL > ------------ > > Key: HBASE-22648 > URL: https://issues.apache.org/jira/browse/HBASE-22648 > Project: HBase > Issue Type: New Feature > Components: snapshots > Affects Versions: 3.0.0 > Reporter: Andrew Purtell > Assignee: Viraj Jasani > Priority: Minor > Fix For: 3.0.0 > > Attachments: HBASE-22648-master-v2.patch, HBASE-22648-master.patch, > Screen Shot 2019-07-10 at 8.49.13 PM.png, Screen Shot 2019-07-10 at 8.52.30 > PM.png, Screen Shot 2019-07-10 at 9.06.36 PM.png > > > Snapshots have a lifecycle that is independent from the table from which they > are created. Although data in a table may be stored with TTL the data files > containing them become frozen by the snapshot. Space consumed by expired > cells will not be reclaimed by normal table housekeeping like compaction. > While this is expected it can be inconvenient at scale. When many snapshots > are under management and the data in various tables is expired by TTL some > notion of optional TTL (and optional default TTL) for snapshots could be > useful. It will help prevent the accumulation of junk files by automatically > dropping the snapshot after the assigned TTL, making their data files > eligible for cleaning. More comprehensive snapshot lifecycle management may > be considered in the future but this one case is expected to be immediately > useful given TTls on data are commonly applied for similar convenience. -- This message was sent by Atlassian JIRA (v7.6.14#76016)