[
https://issues.apache.org/jira/browse/MAPREDUCE-3572?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13180127#comment-13180127
]
Hudson commented on MAPREDUCE-3572:
-----------------------------------
Integrated in Hadoop-Mapreduce-0.23-Commit #351 (See
[https://builds.apache.org/job/Hadoop-Mapreduce-0.23-Commit/351/])
Merge -c 1227426 from trunk to branch-0.23 to fix MAPREDUCE-3572. Moved AM
event dispatcher to a separate thread for performance reasons.
acmurthy :
http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1227428
Files :
* /hadoop/common/branches/branch-0.23/hadoop-mapreduce-project/CHANGES.txt
*
/hadoop/common/branches/branch-0.23/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-app/src/main/java/org/apache/hadoop/mapreduce/v2/app/rm/RMCommunicator.java
*
/hadoop/common/branches/branch-0.23/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-app/src/main/java/org/apache/hadoop/mapreduce/v2/app/rm/RMContainerAllocator.java
*
/hadoop/common/branches/branch-0.23/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-app/src/test/java/org/apache/hadoop/mapreduce/v2/app/TestRMContainerAllocator.java
> MR AM's dispatcher is blocked by heartbeats to ResourceManager
> --------------------------------------------------------------
>
> Key: MAPREDUCE-3572
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-3572
> Project: Hadoop Map/Reduce
> Issue Type: Sub-task
> Components: mr-am, mrv2, performance
> Affects Versions: 0.23.0
> Reporter: Vinod Kumar Vavilapalli
> Assignee: Vinod Kumar Vavilapalli
> Priority: Critical
> Fix For: 0.23.1
>
> Attachments: MAPREDUCE-3572-20111215.txt, MAPREDUCE-3572-20120104.txt
>
>
> All the heartbeat processing is done in {{RMContainerAllocator}} locking the
> object. The event processing is also locked on this, causing the dispatcher
> to be blocked and the rest of the AM getting stalled.
> The event processing should be in a separate thread.
--
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
