[
https://issues.apache.org/jira/browse/FLINK-5791?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
shuai.xu updated FLINK-5791:
----------------------------
Description:
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.
was:
In flip6, for yarn mode, resource should be assigned as requested to avoid
resource wasting and OOM.
1. YarnResourceManager will request container according to ResourceProfile in
slot request form JM.
2. RM will pass the ResourceProfile to TM for initializing its slots.
3. RM should match the slots offered by TM with SlotRequest from JM strictly.
> 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.3.15#6346)
