You are viewing a plain text version of this content. The canonical link for it is here.
Posted to yarn-issues@hadoop.apache.org by "Hudson (JIRA)" <ji...@apache.org> on 2018/08/14 15:49:00 UTC
[jira] [Commented] (YARN-8640) Restore previous state in
container-executor after failure
[ https://issues.apache.org/jira/browse/YARN-8640?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16579982#comment-16579982 ]
Hudson commented on YARN-8640:
------------------------------
SUCCESS: Integrated in Jenkins build Hadoop-trunk-Commit #14766 (See [https://builds.apache.org/job/Hadoop-trunk-Commit/14766/])
YARN-8640. Restore previous state in container-executor after failure. (jlowe: rev d1d129aa9deecebf42261947fcb0b2ca46dacad5)
* (edit) hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager/src/main/native/container-executor/impl/container-executor.c
> Restore previous state in container-executor after failure
> ----------------------------------------------------------
>
> Key: YARN-8640
> URL: https://issues.apache.org/jira/browse/YARN-8640
> Project: Hadoop YARN
> Issue Type: Bug
> Reporter: Jim Brennan
> Assignee: Jim Brennan
> Priority: Major
> Attachments: YARN-8640.001.patch
>
>
> The container-executor function {{write_exit_code_file_as_nm}} had a number of failure conditions where it just returns -1 without restoring previous state.
> This is not a problem in any of the places where it is currently called, but it could be a problem if future code changes call it before code that depends on the previous state.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org