Shuyi Chen created FLINK-10848:
----------------------------------

             Summary: 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.6.2, 1.5.5, 1.4.2, 1.3.3
            Reporter: Shuyi Chen
            Assignee: Shuyi Chen


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)

Reply via email to