[ 
https://issues.apache.org/jira/browse/FLINK-7463?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Flink Jira Bot updated FLINK-7463:
----------------------------------
    Labels: auto-deprioritized-major stale-minor  (was: 
auto-deprioritized-major)

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.


> 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: Minor
>              Labels: auto-deprioritized-major, stale-minor
>
> 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.20.1#820001)

Reply via email to