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 2017/08/08 09:26:00 UTC

[jira] [Commented] (FLINK-5791) Support an optimal matching based slot manager for flip6 yarn mode

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

ASF GitHub Bot commented on FLINK-5791:
---------------------------------------

Github user shuai-xu commented on the issue:

    https://github.com/apache/flink/pull/3580
  
    @tillrohrmann Could you please help to review this pr? And there is a question, the pending requests in slot managers are not in order. So requests arrived later may be fulfilled earlier, does this matter?


> Support an optimal matching based slot manager for flip6 yarn mode
> ------------------------------------------------------------------
>
>                 Key: FLINK-5791
>                 URL: https://issues.apache.org/jira/browse/FLINK-5791
>             Project: Flink
>          Issue Type: Improvement
>          Components: YARN
>            Reporter: shuai.xu
>            Assignee: shuai.xu
>              Labels: flip-6
>
> In flip6, for yarn mode, it request containers from yarn according to the resource profile in slot requests. And when slots come back after container starting up, we should supporting an optimal matching based slot manager which can assign the slot to the request whose resource profile closest to it. This could reduce resource waste and avoid OOM.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)