You are viewing a plain text version of this content. The canonical link for it is here.
Posted to mapreduce-dev@hadoop.apache.org by "Todd Lipcon (Resolved) (JIRA)" <ji...@apache.org> on 2011/11/15 01:42:52 UTC
[jira] [Resolved] (MAPREDUCE-3394) Add log guard for a debug
message in ReduceTask
[ https://issues.apache.org/jira/browse/MAPREDUCE-3394?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Todd Lipcon resolved MAPREDUCE-3394.
------------------------------------
Resolution: Fixed
Fix Version/s: 0.20.206.0
Hadoop Flags: Reviewed
Committed to branch-20-security for 0.20.206. Thanks Eli.
> Add log guard for a debug message in ReduceTask
> -----------------------------------------------
>
> Key: MAPREDUCE-3394
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-3394
> Project: Hadoop Map/Reduce
> Issue Type: Improvement
> Components: task
> Affects Versions: 0.20.205.0
> Reporter: Todd Lipcon
> Assignee: Todd Lipcon
> Priority: Trivial
> Fix For: 0.20.206.0
>
> Attachments: mr-3394.txt
>
>
> There's a LOG.debug message in ReduceTask that stringifies a task ID and uses a non-negligible amount of CPU in some cases. We should guard it with {{isDebugEnabled}}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira