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

["Jonathan Eagles (JIRA)" <ji...@apache.org>]

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

Jonathan Eagles edited comment on TEZ-2282 at 5/8/15 8:27 PM:
--------------------------------------------------------------

+1. Thanks for the patch, [~mitdesai]. I think this is a reasonable way of doing this for now. I can't see a better without using reflection and that just gets messy. If no one else has any more comments, I think we should pull this patch in.


was (Author: jeagles):
+1. Thanks for the patch, [~mitdesai]. I think this is a reasonable way of doing this for now. I can't see a better without using reflection and that just gets messy. If no one else has a better way, I think we should pull this patch in.

> 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-4-branch0.6.patch, TEZ-2282-4-master.patch, TEZ-2282.1.patch, TEZ-2282.2.patch, TEZ-2282.3.master.patch, TEZ-2282.3.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)