[
https://issues.apache.org/jira/browse/FLINK-1683?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Fabian Hueske resolved FLINK-1683.
----------------------------------
Resolution: Fixed
Fixed in 0.9 with 07a9a56c1726b4a7aeb3e682b887d77ab1b0e440
Fixed in 0.8 with 095301e025a87608f3b8785d02580da7f87f1e76
> Scheduling preferences for non-unary tasks are not correctly computed
> ---------------------------------------------------------------------
>
> Key: FLINK-1683
> URL: https://issues.apache.org/jira/browse/FLINK-1683
> Project: Flink
> Issue Type: Bug
> Components: JobManager
> Affects Versions: 0.9, 0.8.1
> Reporter: Fabian Hueske
> Assignee: Fabian Hueske
> Fix For: 0.9, 0.8.2
>
>
> When computing scheduling preferences for an execution task, the JobManager
> looks at the assigned instances of all its input execution tasks and returns
> a preference only if not more than 8 instances have been found (if the input
> of a tasks is distributed across more than 8 tasks, local scheduling won't
> help a lot in any case).
> However, the JobManager treats all input execution tasks the same and does
> not distinguish between different logical input. The effect is that a join
> tasks with one broadcasted and one locally forwarded task is not locally
> assigned towards its locally forwarded input.
> This can have a significant impact on the performance of tasks that have more
> than one input and which rely on local forwarding and co-located task
> scheduling.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
