[
https://issues.apache.org/jira/browse/FLINK-5791?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17219627#comment-17219627
]
Andrey Zagrebin edited comment on FLINK-5791 at 10/23/20, 10:31 AM:
--------------------------------------------------------------------
The ticket looks abandoned. I am closing it.
Different slot assignment strategies can be still useful and this is possible
now with the pluggable SlotManager. This can be also actual for declarative
resource management.
Please, reopen this issue or create other issues for custom slot assignment
strategies in future.
was (Author: azagrebin):
The ticket looks abandoned. I am closing it.
Different slot assignment strategies can be still useful and this is possible
now with the pluggable SlotManager. This can be also actual for declarative
resource management.
Please, reopen this issue or other issues for custom slot assignment strategies
in future.
> 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
> 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)
