[
https://issues.apache.org/jira/browse/TEZ-3588?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15838238#comment-15838238
]
Ming Ma commented on TEZ-3588:
------------------------------
Configuration of NM metrics is a global change that applies to all yarn
applications and whether hprof is needed or not, which will tier up NM
dispatcher thread.
Another benefit of getting the status code right is to enable more accurate
data analysis based on the container success rate. It will also allow us to
apply log aggregation policy differently depending on container status code.
> 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)
