You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@kudu.apache.org by "Grant Henke (JIRA)" <ji...@apache.org> on 2019/06/04 15:21:00 UTC
[jira] [Commented] (KUDU-2677) Implement new gflag for backup
history retention
[ https://issues.apache.org/jira/browse/KUDU-2677?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16855828#comment-16855828 ]
Grant Henke commented on KUDU-2677:
-----------------------------------
Per [https://gerrit.cloudera.org/#/c/13265/] and [https://gerrit.cloudera.org/#/c/12327/] it was decided not to add a new flag, but instead to increase the value for the existing flag. That work is done in [https://github.com/apache/kudu/commit/fa1e67f19484a94f9e5f266cf5d622c90b6069b6].
> 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: Critical
> 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)