[
https://issues.apache.org/jira/browse/FLINK-4511?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-4511:
----------------------------------
Labels: auto-deprioritized-major stale-minor (was:
auto-deprioritized-major)
I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help
the community manage its development. I see this issues has been marked as
Minor but is unassigned and neither itself nor its Sub-Tasks have been updated
for 180 days. I have gone ahead and marked it "stale-minor". If this ticket is
still Minor, please either assign yourself or give an update. Afterwards,
please remove the label or in 7 days the issue will be deprioritized.
> Schedule periodic savepoints
> ----------------------------
>
> Key: FLINK-4511
> URL: https://issues.apache.org/jira/browse/FLINK-4511
> Project: Flink
> Issue Type: New Feature
> Components: Runtime / State Backends
> Reporter: Ufuk Celebi
> Priority: Minor
> Labels: auto-deprioritized-major, stale-minor
>
> Allow triggering of periodic savepoints, which are kept in a bounded queue
> (like completed checkpoints currently, but separate).
> If there is no periodic checkpointing enabled, only periodic savepoints
> should be schedulded.
> If periodic checkpointing is enabled, the periodic savepoints should not be
> scheduled independently, but instead the checkpoint scheduler should trigger
> a savepoint instead. This will ensure that no unexpected interference between
> checkpoints and savepoints happens. For this, I would restrict the savepoint
> interval to be a multiple of the checkpointing interval (if enabled).
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
