[
https://issues.apache.org/jira/browse/FLINK-15036?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Till Rohrmann closed FLINK-15036.
---------------------------------
Resolution: Fixed
Fixed via
1.10.0: 560726a796b0de86869bb63ecdbd980d3cdb6a32
1.9.2: 0071401f3dee67f45684d349864f94bf3cc6359a
1.8.3: 2f0e93fa4f1a534c994d2e7da810cb140fe88790
> Container startup error will be handled out side of the YarnResourceManager's
> main thread
> -----------------------------------------------------------------------------------------
>
> Key: FLINK-15036
> URL: https://issues.apache.org/jira/browse/FLINK-15036
> Project: Flink
> Issue Type: Bug
> Components: Deployment / YARN
> Affects Versions: 1.10.0, 1.8.3, 1.9.2
> Reporter: Till Rohrmann
> Assignee: Yang Wang
> Priority: Blocker
> Labels: pull-request-available
> Fix For: 1.10.0, 1.8.3, 1.9.2
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> With FLINK-13184, we replaced the {{NMClient}} with the {{NMClientAsync}}. As
> part of this change, container start up errors are now handled by a callback
> to {{NMClientAsync.CallbackHandler}}. The implementation of
> {{NMClientAsync.CallbackHandler#onStartContainerError}} will be called by the
> {{NMClientAsync}}. Since the implementation does state changing operations,
> it needs to happen inside of the {{YarnResourceManager}} main thread.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
