[
https://issues.apache.org/jira/browse/FLINK-10868?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16727294#comment-16727294
]
Zhenqiu Huang commented on FLINK-10868:
---------------------------------------
I like this idea. It is pretty clean. After failSlot in each JobMaster, the
execution scheduling will fail on
NoResourceAvailableException. Then, all of the logic will be handled by restart
strategy. I will create a PR in coming days.
> Flink's JobCluster ResourceManager doesn't use yarn.maximum-failed-containers
> as limit of resource acquirement
> --------------------------------------------------------------------------------------------------------------
>
> Key: FLINK-10868
> URL: https://issues.apache.org/jira/browse/FLINK-10868
> Project: Flink
> Issue Type: Bug
> Components: YARN
> Affects Versions: 1.6.2, 1.7.0
> Reporter: Zhenqiu Huang
> Assignee: Zhenqiu Huang
> Priority: Major
>
> Currently, YarnResourceManager does use yarn.maximum-failed-containers as
> limit of resource acquirement. In worse case, when new start containers
> consistently fail, YarnResourceManager will goes into an infinite resource
> acquirement process without failing the job. Together with the
> https://issues.apache.org/jira/browse/FLINK-10848, It will quick occupy all
> resources of yarn queue.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
