[
https://issues.apache.org/jira/browse/FLINK-18690?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17168543#comment-17168543
]
Zhu Zhu commented on FLINK-18690:
---------------------------------
Suboptimal case 2: (it is just a potential case to be noted. there no obvious
evidence shows it will happen)
The producer can be assigned to any of its producer execution slot sharing
group, even if some are better than others.
Example - case2.png:
Topology:
A(parallelism=2) -- all-to-all --> C(parallelism=2), B(parallelism=2) –-
forward --> C
Execution edges:
A1->C1, A1->C2, A2->C1, A2->C2; B1->C1, B2->C2
Optimal grouping:
{A1,B1,C1}{A2,B2,C2} -> 2 remote edges
Suboptimal grouping:
{A1,B1,C2}{A2,B2,C1} -> 4 remote edges
Possible solution:
For each vertex, compute a score(=input edges) for each available producer
execution slot sharing group and choose the group with highest score.
> Implement LocalInputPreferredSlotSharingStrategy
> ------------------------------------------------
>
> Key: FLINK-18690
> URL: https://issues.apache.org/jira/browse/FLINK-18690
> Project: Flink
> Issue Type: Sub-task
> Components: Runtime / Coordination
> Reporter: Andrey Zagrebin
> Assignee: Zhu Zhu
> Priority: Major
> Labels: pull-request-available
> Attachments: case1.png
>
>
> Implement ExecutionSlotSharingGroup, SlotSharingStrategy and default
> LocalInputPreferredSlotSharingStrategy.
> The default strategy would be LocalInputPreferredSlotSharingStrategy. It will
> try to reduce remote data exchanges. Subtasks, which are connected and belong
> to the same SlotSharingGroup, tend to be put in the same
> ExecutionSlotSharingGroup.
> See [design
> doc|https://docs.google.com/document/d/10CbCVDBJWafaFOovIXrR8nAr2BnZ_RAGFtUeTHiJplw/edit#heading=h.t4vfmm4atqoy]
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
