[
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 pull-request-available stale-minor (was:
auto-deprioritized-major pull-request-available)
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.
> 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: Minor
> Labels: auto-deprioritized-major, pull-request-available,
> stale-minor
>
> 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)
