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

Posted to issues@flink.apache.org by "Sihua Zhou (JIRA)" <ji...@apache.org> on 2018/02/14 15:10:00 UTC

[jira] [Commented] (FLINK-8044) Introduce scheduling mechanism to satisfy both state locality and input

    [ https://issues.apache.org/jira/browse/FLINK-8044?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16364215#comment-16364215 ] 

Sihua Zhou commented on FLINK-8044:
-----------------------------------

Sorry [~till.rohrmann], finally I can't come up with a perfect algorithm .... and finally we use a naively mechanism which only schedule according to the state size for local recovery. So I think I can't give your a good document...

> Introduce scheduling mechanism to satisfy both state locality and input
> -----------------------------------------------------------------------
>
>                 Key: FLINK-8044
>                 URL: https://issues.apache.org/jira/browse/FLINK-8044
>             Project: Flink
>          Issue Type: New Feature
>          Components: Scheduler
>    Affects Versions: 1.4.0
>            Reporter: Sihua Zhou
>            Priority: Major
>
> For local recovery we need a scheduler to satisfy both state locality and input, but current scheduler allocate resources according to the order of topologically, this can cause bad result if we allocate base on both state and input, so some revision for scheduler is necessary now.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)