[
https://issues.apache.org/jira/browse/FLINK-19219?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-19219:
-----------------------------------
Labels: auto-deprioritized-major auto-deprioritized-minor
pull-request-available (was: auto-deprioritized-major pull-request-available
stale-minor)
Priority: Not a Priority (was: Minor)
This issue was labeled "stale-minor" 7 days ago and has not received any
updates so it is being deprioritized. If this ticket is actually Minor, please
raise the priority and ask a committer to assign you the issue or revive the
public discussion.
> Run JobManager initialization in a separate thread, to make it cancellable
> --------------------------------------------------------------------------
>
> Key: FLINK-19219
> URL: https://issues.apache.org/jira/browse/FLINK-19219
> Project: Flink
> Issue Type: Improvement
> Components: Runtime / Coordination
> Affects Versions: 1.12.0
> Reporter: Robert Metzger
> Priority: Not a Priority
> Labels: auto-deprioritized-major, auto-deprioritized-minor,
> pull-request-available
>
> FLINK-16866 made the job submission non-blocking. The job submission will be
> executed asynchronously in a thread pool, submitted through a future.
> The problem is that we can not cancel a hanging job submission once it is
> running in the threadpool.
> This ticket is about running the initialization in a separate thread, so that
> we can interrupt it.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
