[
https://issues.apache.org/jira/browse/FLINK-10848?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Till Rohrmann resolved FLINK-10848.
-----------------------------------
Resolution: Fixed
Fix Version/s: 1.8.0
1.7.2
1.6.4
Fixed via
1.8.0: 3903b817cb20524aec2c0fbee763e6bf73f5f989
1.7.2: eb7db3aed4e9651ed8624aa7797c5d9f656b2059
1.6.4: 4022836148a9e7cf39859389e644875dcd2a05e4
> Flink's Yarn ResourceManager can allocate too many excess containers
> --------------------------------------------------------------------
>
> Key: FLINK-10848
> URL: https://issues.apache.org/jira/browse/FLINK-10848
> Project: Flink
> Issue Type: Bug
> Components: YARN
> Affects Versions: 1.3.3, 1.4.2, 1.5.5, 1.6.2
> Reporter: Shuyi Chen
> Assignee: Till Rohrmann
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.6.4, 1.7.2, 1.8.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Currently, both the YarnFlinkResourceManager and YarnResourceManager do not
> call removeContainerRequest() on container allocation success. Because the
> YARN AM-RM protocol is not a delta protocol (please see YARN-1902),
> AMRMClient will keep all ContainerRequests that are added and send them to RM.
> In production, we observe the following that verifies the theory: 16
> containers are allocated and used upon cluster startup; when a TM is killed,
> 17 containers are allocated, 1 container is used, and 16 excess containers
> are returned; when another TM is killed, 18 containers are allocated, 1
> container is used, and 17 excess containers are returned.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
