hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MAPREDUCE-5910) MRAppMaster should handle Resync from RM instead of shutting down.
Date Wed, 16 Jul 2014 17:56:07 GMT

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

Hadoop QA commented on MAPREDUCE-5910:

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment 
  against trunk revision .

    {color:green}+1 @author{color}.  The patch does not contain any @author tags.

    {color:green}+1 tests included{color}.  The patch appears to include 1 new or modified
test files.

    {color:green}+1 javac{color}.  The applied patch does not increase the total number of
javac compiler warnings.

    {color:green}+1 javadoc{color}.  There were no new javadoc warning messages.

    {color:green}+1 eclipse:eclipse{color}.  The patch built with eclipse:eclipse.

    {color:green}+1 findbugs{color}.  The patch does not introduce any new Findbugs (version
2.0.3) warnings.

    {color:green}+1 release audit{color}.  The applied patch does not increase the total number
of release audit warnings.

    {color:red}-1 core tests{color}.  The patch failed these unit tests in hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-app:


    {color:green}+1 contrib tests{color}.  The patch passed contrib unit tests.

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

This message is automatically generated.

> MRAppMaster should handle Resync from RM instead of shutting down.
> ------------------------------------------------------------------
>                 Key: MAPREDUCE-5910
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-5910
>             Project: Hadoop Map/Reduce
>          Issue Type: Task
>          Components: applicationmaster
>            Reporter: Rohith
>            Assignee: Rohith
>         Attachments: MAPREDUCE-5910.1.patch, MAPREDUCE-5910.2.patch, MAPREDUCE-5910.3.patch
> The ApplicationMasterService currently sends a resync response to which the AM responds
by shutting down. The MRAppMaster behavior is expected to change to calling resyncing with
the RM. Resync means resetting the allocate RPC sequence number to 0 and the AM should send
its entire outstanding request to the RM. Note that if the AM is making its first allocate
call to the RM then things should proceed like normal without needing a resync. The RM will
return all containers that have completed since the RM last synced with the AM. Some container
completions may be reported more than once.

This message was sent by Atlassian JIRA

View raw message