[
https://issues.apache.org/jira/browse/TEZ-3326?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15450086#comment-15450086
]
Hitesh Shah edited comment on TEZ-3326 at 8/30/16 8:39 PM:
-----------------------------------------------------------
A recent fix in YARN now pushes the contents of the launch container script to
the application logs. Given that change, do we still need this fix?
Or to put it differently, should we be considering enhancing yarn to log some
of these things as part of the launch container script itself instead of having
all apps build the same functionality?
was (Author: hitesh):
A recent fix in YARN now pushes the contents of the launch container script to
the application logs. Given that change, do we still need this fix?
> Display JVM system properties in AM and task logs
> -------------------------------------------------
>
> Key: TEZ-3326
> URL: https://issues.apache.org/jira/browse/TEZ-3326
> Project: Apache Tez
> Issue Type: Improvement
> Reporter: Ming Ma
> Assignee: Eric Badger
> Attachments: TEZ-3326.001.patch, TEZ-3326.002.patch,
> TEZ-3326.003.patch
>
>
> MapReduce displays JVM system properties via config
> {{mapreduce.jvm.system-properties-to-log}} in both AM and task log . This is
> useful to debug env setting such as java version, etc. It is useful to have
> such logging in Tez.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
