[ 
https://issues.apache.org/jira/browse/FLINK-7463?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17336715#comment-17336715
 ] 

Flink Jira Bot commented on FLINK-7463:
---------------------------------------

This issue was labeled "stale-major" 7 ago and has not received any updates so 
it is being deprioritized. If this ticket is actually Major, please raise the 
priority and ask a committer to assign you the issue or revive the public 
discussion.


> 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)

Reply via email to