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

Hadoop QA commented on MAPREDUCE-3572:
--------------------------------------

+1 overall.  Here are the results of testing the latest attachment 
  
http://issues.apache.org/jira/secure/attachment/12509433/MAPREDUCE-3572-20120104.txt
  against trunk revision .

    +1 @author.  The patch does not contain any @author tags.

    +1 tests included.  The patch appears to include 3 new or modified tests.

    +1 javadoc.  The javadoc tool did not generate any warning messages.

    +1 javac.  The applied patch does not increase the total number of javac 
compiler warnings.

    +1 eclipse:eclipse.  The patch built with eclipse:eclipse.

    +1 findbugs.  The patch does not introduce any new Findbugs (version 1.3.9) 
warnings.

    +1 release audit.  The applied patch does not increase the total number of 
release audit warnings.

    +1 core tests.  The patch passed unit tests in .

    +1 contrib tests.  The patch passed contrib unit tests.

Test results: 
https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/1533//testReport/
Console output: 
https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/1533//console

This message is automatically generated.
                
> 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

        

Reply via email to