[jira] [Comment Edited] (TEZ-2282) Delimit reused yarn container logs (stderr, stdout, syslog) with task attempt start/stop events

["Hitesh Shah (JIRA)" <ji...@apache.org>]

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

Hitesh Shah edited comment on TEZ-2282 at 4/15/15 11:27 PM:
------------------------------------------------------------

[~mitdesai] Looking at [~jeagles]'s description, it seems like we should probably add a timestamp to the log message. Maybe prefix the message with a timestamp? Also, it might be helpful to add a log whenever the task completes ( after calling close() ). 

In addition to this, I think it might be good to have the same logic in the DAG App Master for each dag start/stop.



was (Author: hitesh):
[~mitdesai] Looking at [~jeagles]'s description, it seems like we should probably add a timestamp to the log message. Maybe prefix the message with a timestamp? 

> Delimit reused yarn container logs (stderr, stdout, syslog) with task attempt start/stop events
> -----------------------------------------------------------------------------------------------
>
>                 Key: TEZ-2282
>                 URL: https://issues.apache.org/jira/browse/TEZ-2282
>             Project: Apache Tez
>          Issue Type: Bug
>            Reporter: Jonathan Eagles
>            Assignee: Mit Desai
>         Attachments: TEZ-2282.1.patch, TEZ-2282.2.patch, TEZ-2282.master.1.patch
>
>
> This could help with debugging in some cases where logging is task specific. For example GC log is going to stdout, it will be nice to see task attempt start/stop times



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)