[
https://issues.apache.org/jira/browse/FLINK-7463?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17328733#comment-17328733
]
Flink Jira Bot commented on FLINK-7463:
---------------------------------------
This major issue is unassigned and itself and all of its Sub-Tasks have not
been updated for 30 days. So, it has been labeled "stale-major". If this ticket
is indeed "major", please either assign yourself or give an update. Afterwards,
please remove the label. In 7 days the issue will be deprioritized.
> Release nascent workers on slot request timeout
> ------------------------------------------------
>
> Key: FLINK-7463
> URL: https://issues.apache.org/jira/browse/FLINK-7463
> Project: Flink
> Issue Type: Improvement
> Components: Runtime / Coordination
> Reporter: Eron Wright
> Priority: Major
> Labels: stale-major
>
> A slot request causes a new worker to be allocated. If the slot request
> times out or is cancelled before the worker is launched, cancel the worker
> request if possible.
> This is an optimization because an idle slot is eventually released anyway.
> However, I observe that a lot of worker requests pile up in the launch
> coordinator, as the JM keeps making request after request.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
