[jira] [Commented] (KUDU-2677) Implement new gflag for backup history retention

["Will Berkeley (JIRA)" <ji...@apache.org>]

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

Will Berkeley commented on KUDU-2677:
-------------------------------------

We decided it doesn't make sense to separate the latest time when history is scannable and the latest time before it can be GC'd. In other words, this JIRA just requests a flag so that {{AHM = now - max(old_flag, new_flag)}}.

> Implement new gflag for backup history retention
> ------------------------------------------------
>
>                 Key: KUDU-2677
>                 URL: https://issues.apache.org/jira/browse/KUDU-2677
>             Project: Kudu
>          Issue Type: Improvement
>            Reporter: Grant Henke
>            Assignee: Will Berkeley
>            Priority: Major
>              Labels: backup
>
> Implement separate gflag (perhaps --backup_max_incremental_age_sec) for non-snapshot history retention separate from --tablet_history_max_age_sec; Actual retention will be maximum of these two flags, but regular scans still may only scan after --tablet_history_max_age_sec. This makes it possible to implement snapshots in future releases by retiring or changing the semantics of the --tablet_history_max_age_sec flag.
> Overall this help support backup jobs that run for an extended period of time. 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)