[
https://issues.apache.org/jira/browse/HIVE-17078?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16087586#comment-16087586
]
Sahil Takiar commented on HIVE-17078:
-------------------------------------
Ok sounds good.
Few other comments:
* Can you change the thread name to include something about the child process?
Right now it just includes the current threads id + stderr / stdout which seems
to suggest the logs the stderr / stdout of the specified thread, which isn't
the case
* Where does {{l4j}} print to?
* You can use {{StringUtils.stringifyException}} instead of writing the stack
trace to a {{StringOutputStream}}
> Add more logs to MapredLocalTask
> --------------------------------
>
> Key: HIVE-17078
> URL: https://issues.apache.org/jira/browse/HIVE-17078
> Project: Hive
> Issue Type: Improvement
> Reporter: Yibing Shi
> Assignee: Yibing Shi
> Priority: Minor
> Attachments: HIVE-17078.1.patch, HIVE-17078.2.patch,
> HIVE-17078.3.patch, HIVE-17078.4.PATCH
>
>
> By default, {{MapredLocalTask}} is executed in a child process of Hive, in
> case the local task uses too much resources that may affect Hive. Currently,
> the stdout and stderr information of the child process is printed in Hive's
> stdout/stderr log, which doesn't have a timestamp information, and is
> separated from Hive service logs. This makes it hard to troubleshoot problems
> in MapredLocalTasks.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
