You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2020/06/01 08:28:00 UTC
[jira] [Updated] (FLINK-18034) Introduce
PreferredLocationsRetriever
[ https://issues.apache.org/jira/browse/FLINK-18034?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
ASF GitHub Bot updated FLINK-18034:
-----------------------------------
Labels: pull-request-available (was: )
> Introduce PreferredLocationsRetriever
> -------------------------------------
>
> Key: FLINK-18034
> URL: https://issues.apache.org/jira/browse/FLINK-18034
> Project: Flink
> Issue Type: Sub-task
> Components: Runtime / Coordination
> Reporter: Zhu Zhu
> Assignee: Zhu Zhu
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.12.0
>
>
> Preferred locations based on state and inputs are scattered into multiple components, which makes it harder to reasoning the calculation and complicates those hosting components.
> We can introduce a {{PreferredLocationsRetriever}} to be used by {{ExecutionSlotAllocator}} which returns preferred locations of an execution vertex and hides the details of the calculation from other components.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)