You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Till Rohrmann (Jira)" <ji...@apache.org> on 2019/12/04 10:17:00 UTC
[jira] [Assigned] (FLINK-15036) Container startup error will be
handled out side of the YarnResourceManager's main thread
[ https://issues.apache.org/jira/browse/FLINK-15036?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Till Rohrmann reassigned FLINK-15036:
-------------------------------------
Assignee: Yang Wang
> 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: Critical
> Labels: pull-request-available
> Fix For: 1.10.0, 1.8.3, 1.9.2
>
> Time Spent: 10m
> 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)