hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jim Brennan (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-8640) Restore previous state in container-executor if write_exit_code_file_as_nm fails
Date Mon, 13 Aug 2018 16:17:00 GMT

    [ https://issues.apache.org/jira/browse/YARN-8640?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16578547#comment-16578547
] 

Jim Brennan commented on YARN-8640:
-----------------------------------

Tested by running test-container-executor and cetest - both pass with no errors.  Also ran
sleep and pi jobs on a single node cluster with and without docker, and also with NM restart
during the jobs.

[~jlowe] please review.

 

> Restore previous state in container-executor if write_exit_code_file_as_nm fails
> --------------------------------------------------------------------------------
>
>                 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


Mime
View raw message