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

Sen Zhao commented on MAPREDUCE-7050:
-------------------------------------

Could someone add me into the contributor list ? So that I can submit a patch.

> Debug logs should be improvement
> --------------------------------
>
>                 Key: MAPREDUCE-7050
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-7050
>             Project: Hadoop Map/Reduce
>          Issue Type: Improvement
>            Reporter: Sen Zhao
>            Priority: Minor
>
> I noticed that in Mapreduced code, there are many places to use Log.debug as 
> follows:
> {code}
> LOG.debug("example " + example.getClass().getName() + "example" );
> {code}
> When the system loglevel set higher than Debug, although the system does not 
> print these levels of logs, but each time will splicing parameters string, 
> affect system performance.
> It should be:
> {code}
> if(LOG.isDebugEnabled()){
>     LOG.debug("example " + example.getClass().getName() + "example" );
> }
> {code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: mapreduce-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: mapreduce-issues-h...@hadoop.apache.org

Reply via email to