[
https://issues.apache.org/jira/browse/TEZ-3562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15754752#comment-15754752
]
Jonathan Eagles commented on TEZ-3562:
--------------------------------------
Users wanted to be able to use their existing UDFs without change. Many UDFs
log directly to stdout and stderr. It's possible we could offer some
configuration that would disable logging this message completely. If there was
a container launcher that didn't log automatically to stdout and stderr, this
might be helpful. However, in all the cases of containers that fail during
initialization, the stdout and stderr file is one of the few hints the user has
to understand what happened.
Is there something specific that we are trying to avoid here or a goal we are
trying to achieve? That may give me background on this issue and a way forward.
> Attempt completion gets printed to STDOUT and STDERR
> ----------------------------------------------------
>
> Key: TEZ-3562
> URL: https://issues.apache.org/jira/browse/TEZ-3562
> Project: Apache Tez
> Issue Type: Bug
> Affects Versions: 0.9.0, 0.8.4
> Reporter: Prasanth Jayachandran
> Assignee: Prasanth Jayachandran
> Priority: Trivial
> Attachments: TEZ-3562.1.patch
>
>
> LogicalIOProcessorRuntimeTask.java is printing the attempt completion msg
> twice (once to STDOUT and another to STDERR). Should this go into log file
> once at INFO level instead?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
