[
https://issues.apache.org/jira/browse/MAPREDUCE-5910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14048824#comment-14048824
]
Hadoop QA commented on MAPREDUCE-5910:
--------------------------------------
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12653384/MAPREDUCE-5910.2.patch
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 1.3.9) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-app
hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-core.
{color:green}+1 contrib tests{color}. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/4701//testReport/
Console output:
https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/4701//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
> Fix For: 2.5.0
>
> Attachments: MAPREDUCE-5910.1.patch, MAPREDUCE-5910.2.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
(v6.2#6252)
