[
https://issues.apache.org/jira/browse/FLINK-9410?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16492455#comment-16492455
]
ASF GitHub Bot commented on FLINK-9410:
---------------------------------------
Github user sihuazhou commented on the issue:
https://github.com/apache/flink/pull/6087
Hi @zhangminglei , I would suggest to retry, this is more consistent with
the behavior when we are using the sync API, in fact, currently if we don't
retry to start container then the job will fail to acquire slots, and RM will
also stop to start container for the jobs that are waiting for slots.
> Replace NMClient with NMClientAsync in YarnResourceManager
> ----------------------------------------------------------
>
> Key: FLINK-9410
> URL: https://issues.apache.org/jira/browse/FLINK-9410
> Project: Flink
> Issue Type: Improvement
> Components: Distributed Coordination
> Affects Versions: 1.5.0, 1.6.0
> Reporter: Till Rohrmann
> Assignee: mingleizhang
> Priority: Critical
> Fix For: 1.6.0
>
>
> Currently, the {{YarnResourceManager}} uses the synchronous {{NMClient}}
> which is called from within the main thread of the {{ResourceManager}}. Since
> these operations are blocking, we should replace the client with the
> {{NMClientAsync}} and make the calls non blocking.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
