[
https://issues.apache.org/jira/browse/FLINK-24113?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17459560#comment-17459560
]
Chesnay Schepler commented on FLINK-24113:
------------------------------------------
I'm not sure what the best alternative is. We ignore interrupts there for a
reason; without it the whole cluster can crash on Java 11 if some signal hits
the JVM. For this particular case we could amend {{#acceptWithoutTimeout}} to
accept a {{Supplier<Boolean>}} for whether it should retry or not; that would
allow the BlobServer to shut down.
Whether that'd work for all other places where this is used remains to be seen.
> Introduce option in Application Mode to disable 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
> Assignee: Nicolaus Weidner
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.15.0
>
> Attachments: shutdown_issue.log
>
>
> 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.20.1#820001)
