-
Type:
Bug
-
Status: Resolved
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 1.3.3, 1.4.2, 1.5.5, 1.6.2
-
Component/s: Deployment / YARN
-
Labels:
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.
- is duplicated by
-
FLINK-10735 flink on yarn close container exception
-
- Closed
-
-
FLINK-11149 Flink will request too more containers than it actually needs
-
- Closed
-
- links to