[
https://issues.apache.org/jira/browse/MAPREDUCE-4629?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13449867#comment-13449867
]
Karthik Kambatla commented on MAPREDUCE-4629:
---------------------------------------------
The DEBUG_MODE seems to be doing a lot of things. It has a shorter cleanup time
for history files, history filenames use different timestamps, prints stack
traces at various points in the code.
Given that the config option was not present in the mapred-default.xml so far,
I wonder if anyone is aware of and using DEBUG_MODE at all. One option is to
remove the DEBUG_MODE and do the following instead:
- Add a config-parameter for history cleanup
- Replace instances of debug-printing with LOG.debug()
- To address the ability to verify shorter cleanup times, add the hour/min to
the history filenames.
> In DEBUG_MODE, JobHistory#directoryTime() returns incorrect time
> ----------------------------------------------------------------
>
> Key: MAPREDUCE-4629
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-4629
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Affects Versions: 1.0.3
> Reporter: Karthik Kambatla
> Assignee: Karthik Kambatla
> Attachments: MR-4629.patch, MR-4629.patch.v1
>
>
> The helper methods in JobHistory - directoryTime() and
> timestampDirectoryComponent() - adjust the month field for readability (Jan
> is 0 as per Calendar, 1 for us)
> In DEBUG_MODE, JobHistory uses hour instead of month. However, the adjustment
> is still applied.
--
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
