[
https://issues.apache.org/jira/browse/FLINK-6049?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-6049:
----------------------------------
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.
> Parallelize execution of (async) snapshots in AsyncCheckpointRunnable
> ---------------------------------------------------------------------
>
> Key: FLINK-6049
> URL: https://issues.apache.org/jira/browse/FLINK-6049
> Project: Flink
> Issue Type: Improvement
> Components: Runtime / State Backends
> Affects Versions: 1.3.0
> Reporter: Stefan Richter
> Priority: Minor
> Labels: auto-deprioritized-major, stale-minor
>
> After the changes from [FLINK-6048], it would make sense to parallelize the
> execution of the `RunnableFuture`s of (async) snapshot in
> `AsyncCheckpointRunnable`. Currently, `AsyncCheckpointRunnable` is a thread
> that runs parallel, but executes each snapshot sequentially. The reason is,
> that previously only keyed state backends had support for async snapshots.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
