[
https://issues.apache.org/jira/browse/FLINK-5791?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17194196#comment-17194196
]
Andrey Zagrebin commented on FLINK-5791:
----------------------------------------
SlotManager can have different implementation now (FLINK-14106).
[~tiemsn] are you still planning to work on this?
> 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: Deployment / YARN
> Reporter: shuai.xu
> Assignee: shuai.xu
> Priority: Major
> Labels: flip-6, pull-request-available
> Time Spent: 10m
> Remaining Estimate: 0h
>
> 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
(v8.3.4#803005)
