[
https://issues.apache.org/jira/browse/TEZ-3326?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eric Badger updated TEZ-3326:
-----------------------------
Attachment: TEZ-3326.003.patch
bq. Scope.VERTEX reflects whether this config can be changed on a per
dag/vertex basis and if yes, it should take effect. In this case, I think AM is
better as this is mainly for logging only when a container starts up and has no
impact when a new dag/task is run.
[~hitesh], thanks for the explanation. I had an incorrect understanding of the
scope annotation. I'm attaching a patch that changes the scope back to AM.
> 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)
