[
https://issues.apache.org/jira/browse/FLINK-24113?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17408498#comment-17408498
]
Yang Wang commented on FLINK-24113:
-----------------------------------
Maybe we could add an optional argument to the "stop-with-savepoint" operation
whether to wait for the savepoint result. If it is true, the Flink application
should only shutdown after the savepoint result has been retrieved by someone.
> Introduce option in Application Mode to request cluster shutdown
> ----------------------------------------------------------------
>
> Key: FLINK-24113
> URL: https://issues.apache.org/jira/browse/FLINK-24113
> Project: Flink
> Issue Type: Improvement
> Components: Runtime / Coordination
> Affects Versions: 1.15.0
> Reporter: Robert Metzger
> Priority: Major
>
> Currently a Flink JobManager started in Application Mode will shut down once
> the job has completed.
> When doing a "stop with savepoint" operation, we want to keep the JobManager
> alive after the job has stopped to retrieve and persist the final savepoint
> location.
> Currently, Flink waits up to 5 minutes and then shuts down.
> I'm proposing to introduce a new configuration flag "application mode
> shutdown behavior": "keepalive" (naming things is hard ;) ) which will keep
> the JobManager in ApplicationMode running until a REST call confirms that it
> can shutdown.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
