You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@flink.apache.org by "Till Rohrmann (Jira)" <ji...@apache.org> on 2019/12/03 11:03:00 UTC

[jira] [Created] (FLINK-15036) Container startup error will be handled out side of the YarnResourceManager's main thread

Till Rohrmann created FLINK-15036:
-------------------------------------

             Summary: 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
             Fix For: 1.10.0, 1.8.3, 1.9.2


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)