[
https://issues.apache.org/jira/browse/TEZ-2282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14497377#comment-14497377
]
Mit Desai commented on TEZ-2282:
--------------------------------
bq. it seems like we should probably add a timestamp to the log message
I thought having a start point to differentiate was the purpose. But I can
definitely work on getting the timestamp.
I will also do the same when the task completes and in the DAG App Master
start/stop logic.
> 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)
