[
https://issues.apache.org/jira/browse/FLINK-6480?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17328778#comment-17328778
]
Flink Jira Bot commented on FLINK-6480:
---------------------------------------
This major issue is unassigned and itself and all of its Sub-Tasks have not
been updated for 30 days. So, it has been labeled "stale-major". If this ticket
is indeed "major", please either assign yourself or give an update. Afterwards,
please remove the label. In 7 days the issue will be deprioritized.
> Add executor service parameter Snapshotable::snapshot(...)
> ----------------------------------------------------------
>
> Key: FLINK-6480
> URL: https://issues.apache.org/jira/browse/FLINK-6480
> Project: Flink
> Issue Type: Improvement
> Components: Runtime / State Backends
> Reporter: Stefan Richter
> Priority: Major
> Labels: stale-major
>
> We could change the way how async snapshots are executed. Currently, the
> snapshot method looks like:
> {code:java}
> RunnableFuture<S> snapshot(
> long checkpointId,
> long timestamp,
> CheckpointStreamFactory streamFactory,
> CheckpointOptions checkpointOptions) throws Exception;
> {code}
> and I would suggest to change this to:
> {code:java}
> Future<S> snapshot(
> long checkpointId,
> long timestamp,
> CheckpointStreamFactory streamFactory,
> CheckpointOptions checkpointOptions,
> ExecutorService executor) throws Exception;
> {code}
> The implication of this change is, that the FutureRunnable can immediately be
> scheduled to the provided executor service. This makes it easier to reason
> about the Future's lifecycle and to parallelize multiple snapshot tasks in an
> operator instance's checkpointing.
> The Future's ownership is only transferred once, from the backend to the
> executor service, so cancelation on shutdown only either happens already in
> the backend or when the executor service is shut down.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
