You are viewing a plain text version of this content. The canonical link for it is here.

Posted to mapreduce-issues@hadoop.apache.org by "Karthik Kambatla (JIRA)" <ji...@apache.org> on 2012/09/07 01:45:08 UTC

[jira] [Commented] (MAPREDUCE-4629) Remove JobHistory.DEBUG_MODE

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

Karthik Kambatla commented on MAPREDUCE-4629:
---------------------------------------------

Modified this JIRA to remove the DEBUG_MODE. Created https://issues.apache.org/jira/browse/MAPREDUCE-4643 to make the cleanup period configurable. 
                
> Remove JobHistory.DEBUG_MODE
> ----------------------------
>
>                 Key: MAPREDUCE-4629
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-4629
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>    Affects Versions: 1.0.3, 2.0.0-alpha
>            Reporter: Karthik Kambatla
>            Assignee: Karthik Kambatla
>         Attachments: MR-4629.patch, MR-4629.patch.v1
>
>
> Remove JobHistory.DEBUG_MODE for the following reasons:
> 1. No one seems to be using it - the config parameter corresponding to enabling it does not even exist in mapred-default.xml
> 2. The logging being done in DEBUG_MODE needs to move to LOG.debug() and LOG.trace()
> 3. Buggy handling of helper methods in DEBUG_MODE; e.g. directoryTime() and timestampDirectoryComponent().

--
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