[
https://issues.apache.org/jira/browse/FLINK-20095?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-20095:
-----------------------------------
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.
> SchedulerBase.stopWithSavepoint schedules operation after ExecutionGraph
> terminates
> -----------------------------------------------------------------------------------
>
> Key: FLINK-20095
> URL: https://issues.apache.org/jira/browse/FLINK-20095
> Project: Flink
> Issue Type: Improvement
> Components: Runtime / Coordination
> Affects Versions: 1.12.0
> Reporter: Till Rohrmann
> Priority: Minor
> Labels: auto-deprioritized-major, stale-minor
>
> While looking into FLINK-20065, we realized that we cannot implement the
> change described in FLINK-20094 because the {{SchedulerBase}} schedules an
> asynchronous operation after the termination of the {{ExecutionGraph}}. This
> asynchronous operation needs to complete before the savepoint path is
> returned.
> In order to solve FLINK-20094, we either need to keep track of these
> operations and suspend the {{SchedulerBase}} termination until all operations
> have completed or we might be able to return the savepoint path without
> depending it on the completion of the {{handleAsync}} here:
> https://github.com/apache/flink/blob/master/flink-runtime/src/main/java/org/apache/flink/runtime/scheduler/SchedulerBase.java#L921.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
