You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hive.apache.org by "Barna Zsombor Klara (JIRA)" <ji...@apache.org> on 2017/09/19 08:07:01 UTC

[jira] [Commented] (HIVE-17078) Add more logs to MapredLocalTask

    [ https://issues.apache.org/jira/browse/HIVE-17078?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16171261#comment-16171261 ] 

Barna Zsombor Klara commented on HIVE-17078:
--------------------------------------------

Hi [~Yibing],
do you have the free time to do the refactoring suggested by Peter? If not then I'd be happy to add the final touch. The patch looks good, so it would be a shame to not commit it.

> 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, HIVE-17078.5.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)