[
https://issues.apache.org/jira/browse/MAPREDUCE-4614?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13446333#comment-13446333
]
Daryn Sharp commented on MAPREDUCE-4614:
----------------------------------------
I'm ok with INFO during stabilization. As you mention, the problem with client
DEBUG log level is we miss the bugs "in the act". Plus we've had enough job
submission issues lately that affect oozie which are painfully hard to debug.
It's been indispensable to see the submitted tokens, see if the launcher task
acquired them, whether the launcher task's job submission sent them along,
followed by whether they popped out in the other job.
> Simplify debugging a job's tokens
> ---------------------------------
>
> Key: MAPREDUCE-4614
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-4614
> Project: Hadoop Map/Reduce
> Issue Type: Improvement
> Components: client, task
> Affects Versions: 0.23.3, 3.0.0, 2.2.0-alpha
> Reporter: Daryn Sharp
> Assignee: Daryn Sharp
> Attachments: MAPREDUCE-4614.branch-23.patch, MAPREDUCE-4614.patch
>
>
> It's exceedingly difficult to debug token issues with a job. Sometimes
> tokens appear to be missing, or have the wrong service, etc. It would be
> much easier if job submission logged the tokens submitted, and if tasks
> logged the tokens they received.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
