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 2019/11/24 15:18:00 UTC

[jira] [Closed] (FLINK-14314) Allocate shared slot resources respecting the resources of all vertices in the group

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

Chesnay Schepler closed FLINK-14314.
------------------------------------
    Resolution: Fixed

master: bc241861f2425a2f926262a924e271227382b38a

> Allocate shared slot resources respecting the resources of all vertices in the group
> ------------------------------------------------------------------------------------
>
>                 Key: FLINK-14314
>                 URL: https://issues.apache.org/jira/browse/FLINK-14314
>             Project: Flink
>          Issue Type: Sub-task
>          Components: Runtime / Coordination
>    Affects Versions: 1.10.0
>            Reporter: Zhu Zhu
>            Assignee: Zhu Zhu
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 1.10.0
>
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> With FLINK-14058, it is assumed that a shared slot should be large enough to be used by one instance of each JobVertex in the group simultaneously.
> To support it, a shared slot resources should be the sum of all JobVertex resources in the group.
> Here's the concrete proposal:
> 1. Add a physicalSlotResourceProfile in SlotProfile. If the task is not in a shared slot, it is the task resource profile. Otherwise it is the slot sharing group resource profile. It should be used for physical slot allocation. Rename previous ResourceProfile to be taskResourceProfile for logical slot allocation.
> 2. SharedSlotOversubscribedException and its handling can be removed, including part of the children slots releasing and re-allocating. This is because partial fulfillment should not happen anymore with #1. A simple sanity check can be kept for oversubscribing.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)