You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@flink.apache.org by "Andrey Zagrebin (Jira)" <ji...@apache.org> on 2020/08/06 09:54:00 UTC

[jira] [Closed] (FLINK-18739) Implement MergingSharedSlotProfileRetriever

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

Andrey Zagrebin closed FLINK-18739.
-----------------------------------
    Fix Version/s: 1.12.0
       Resolution: Done

merged into master by 13fafa5c51af2741de19d1189e491630026a737f

> Implement MergingSharedSlotProfileRetriever
> -------------------------------------------
>
>                 Key: FLINK-18739
>                 URL: https://issues.apache.org/jira/browse/FLINK-18739
>             Project: Flink
>          Issue Type: Sub-task
>          Components: Runtime / Coordination
>            Reporter: Andrey Zagrebin
>            Assignee: Andrey Zagrebin
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 1.12.0
>
>
> Input location preferences will be considered for each SharedSlot when allocating a physical slot for it. Input location preferences of a SharedSlot will be the merge of input location preferences of all the tasks to run in this SharedSlot.
> Inter-ExecutionSlotSharingGroup input location preferences can be respected in this way for ExecutionSlotSharingGroups belonging to different bulks. If ExecutionSlotSharingGroups belong to the same bulk, the input location preferences are ignored because of possible cyclic dependencies. Later, we can optimise this case when the declarative resource management for reactive mode is ready.
> Intra-ExecutionSlotSharingGroup input location preferences will also be respected when creating ExecutionSlotSharingGroup(s) in DefaultSlotSharingStrategy.



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