You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Chesnay Schepler (Jira)" <ji...@apache.org> on 2021/01/29 10:33:00 UTC
[jira] [Assigned] (FLINK-7463) Release nascent workers on slot
request timeout
[ https://issues.apache.org/jira/browse/FLINK-7463?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Chesnay Schepler reassigned FLINK-7463:
---------------------------------------
Assignee: (was: boshu Zheng)
> 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
>
> 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)