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 "Vinod K V (JIRA)" <ji...@apache.org> on 2010/04/08 10:43:36 UTC
[jira] Created: (MAPREDUCE-1685) Debug statements affecting
performance of JobTracker.heartbeat
Debug statements affecting performance of JobTracker.heartbeat
--------------------------------------------------------------
Key: MAPREDUCE-1685
URL: https://issues.apache.org/jira/browse/MAPREDUCE-1685
Project: Hadoop Map/Reduce
Issue Type: Bug
Reporter: Vinod K V
Several debug statements that come in the critical section in JobTracker.heartbeat() are not protected by a LOG.isDebugEnabled() and so incur non-trivial costs, in the order of 15% of the total heartbeat processing time.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (MAPREDUCE-1685) Debug statements affecting
performance of JobTracker.heartbeat
Posted by "Vinod K V (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MAPREDUCE-1685?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Vinod K V updated MAPREDUCE-1685:
---------------------------------
Affects Version/s: 0.20.1
Most of these debug statements are in JobTracker/JobInProgress/CapacityTaskScheduler. It's tested on 0.20 clusters.
> Debug statements affecting performance of JobTracker.heartbeat
> --------------------------------------------------------------
>
> Key: MAPREDUCE-1685
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-1685
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Affects Versions: 0.20.1
> Reporter: Vinod K V
>
> Several debug statements that come in the critical section in JobTracker.heartbeat() are not protected by a LOG.isDebugEnabled() and so incur non-trivial costs, in the order of 15% of the total heartbeat processing time.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (MAPREDUCE-1685) Debug statements affecting
performance of JobTracker.heartbeat
Posted by "Vinod K V (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MAPREDUCE-1685?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Vinod K V resolved MAPREDUCE-1685.
----------------------------------
Fix Version/s: 0.22.0
Resolution: Duplicate
This is being fixed as part of MAPREDUCE-1533.
> Debug statements affecting performance of JobTracker.heartbeat
> --------------------------------------------------------------
>
> Key: MAPREDUCE-1685
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-1685
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Affects Versions: 0.20.1
> Reporter: Vinod K V
> Fix For: 0.22.0
>
>
> Several debug statements that come in the critical section in JobTracker.heartbeat() are not protected by a LOG.isDebugEnabled() and so incur non-trivial costs, in the order of 15% of the total heartbeat processing time.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (MAPREDUCE-1685) Debug statements affecting
performance of JobTracker.heartbeat
Posted by "Xiao Kang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MAPREDUCE-1685?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12854879#action_12854879 ]
Xiao Kang commented on MAPREDUCE-1685:
--------------------------------------
Any more details? Which version of hadoop the 15% is profied on?
> Debug statements affecting performance of JobTracker.heartbeat
> --------------------------------------------------------------
>
> Key: MAPREDUCE-1685
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-1685
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Reporter: Vinod K V
>
> Several debug statements that come in the critical section in JobTracker.heartbeat() are not protected by a LOG.isDebugEnabled() and so incur non-trivial costs, in the order of 15% of the total heartbeat processing time.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.