You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Zhu Zhu (Jira)" <ji...@apache.org> on 2020/05/25 06:30:00 UTC
[jira] [Closed] (FLINK-17542) Unify slot request timeout handling
for streaming and batch tasks
[ https://issues.apache.org/jira/browse/FLINK-17542?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Zhu Zhu closed FLINK-17542.
---------------------------
Resolution: Abandoned
Superseded by FLINK-17018.
> Unify slot request timeout handling for streaming and batch tasks
> -----------------------------------------------------------------
>
> Key: FLINK-17542
> URL: https://issues.apache.org/jira/browse/FLINK-17542
> Project: Flink
> Issue Type: Sub-task
> Components: Runtime / Coordination
> Affects Versions: 1.11.0
> Reporter: Zhu Zhu
> Assignee: Zhu Zhu
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.12.0
>
>
> There are 2 different slot request timeout handling mechanism for batch and streaming tasks.
> For streaming tasks, the slot request will fail if it is not fulfilled within slotRequestTimeout.
> For batch tasks, the slot request will be checked periodically to see whether it is fulfillable, and only fails if it has been unfulfillable for a certain period(slotRequestTimeout).
> With slot marked with whether they will be occupied indefinitely, we can unify these handling. See [FLIP-119|https://cwiki.apache.org/confluence/display/FLINK/FLIP-119+Pipelined+Region+Scheduling#FLIP-119PipelinedRegionScheduling-ExtendedSlotProviderInterface] for more details.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)