You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@tez.apache.org by "Gopal V (JIRA)" <ji...@apache.org> on 2017/01/24 22:09:26 UTC
[jira] [Commented] (TEZ-3588) Tez containers exiting with Yarn
status = -105 (killed by app master) instead of 0
[ https://issues.apache.org/jira/browse/TEZ-3588?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15836732#comment-15836732 ]
Gopal V commented on TEZ-3588:
------------------------------
The NM can be configured around this problem {{yarn.nodemanager.sleep-delay-before-sigkill.ms}} + {{yarn.nodemanager.process-kill-wait.ms}}
> Tez containers exiting with Yarn status = -105 (killed by app master) instead of 0
> ----------------------------------------------------------------------------------
>
> Key: TEZ-3588
> URL: https://issues.apache.org/jira/browse/TEZ-3588
> Project: Apache Tez
> Issue Type: Bug
> Reporter: Piyush Narang
>
> Noticed that Tez containers on exit aren't setting the containerExitStatus to 0. Instead they seem to be setting this to -105 (killed by app master). This is the case even when the DAG succeeds and the given container completed successfully.
> Chatting with [~mingma] and he mentioned that this might require a fix similar to what was done in case of Hadoop - https://issues.apache.org/jira/browse/MAPREDUCE-5465.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)