You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Stephan Ewen (JIRA)" <ji...@apache.org> on 2016/09/02 15:41:20 UTC
[jira] [Commented] (FLINK-4525) Drop the "eager split
pre-assignment" code paths
[ https://issues.apache.org/jira/browse/FLINK-4525?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15458851#comment-15458851 ]
Stephan Ewen commented on FLINK-4525:
-------------------------------------
Addendum in fb8f2c935e96c9300a7584e310eb96e8a1f32f7f
> Drop the "eager split pre-assignment" code paths
> ------------------------------------------------
>
> Key: FLINK-4525
> URL: https://issues.apache.org/jira/browse/FLINK-4525
> Project: Flink
> Issue Type: Improvement
> Components: JobManager
> Affects Versions: 1.1.2
> Environment:
> Reporter: Stephan Ewen
> Assignee: Stephan Ewen
> Fix For: 1.2.0
>
>
> There is currently an interface for input splits {{StrictlyLocalAssignment}} that is half-heartedly supported in the JobManager (it is, for example, not fault tolerant).
> I suggest to drop these special cases for the following reasons:
> - they do not fit the assumptions of all the rest of the system well (localize where possible, but never constrain)
> - they make the logic of implemented as part of dynamic resource acquisition hard
> - they are not fully implemented even today
> - I am not aware of anyone using this feature
> - It is complicated to maintain
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)