Return-Path: X-Original-To: apmail-hadoop-mapreduce-issues-archive@minotaur.apache.org Delivered-To: apmail-hadoop-mapreduce-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 0A63111403 for ; Thu, 17 Jul 2014 08:08:06 +0000 (UTC) Received: (qmail 33393 invoked by uid 500); 17 Jul 2014 08:08:05 -0000 Delivered-To: apmail-hadoop-mapreduce-issues-archive@hadoop.apache.org Received: (qmail 33339 invoked by uid 500); 17 Jul 2014 08:08:05 -0000 Mailing-List: contact mapreduce-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: mapreduce-issues@hadoop.apache.org Delivered-To: mailing list mapreduce-issues@hadoop.apache.org Received: (qmail 33298 invoked by uid 99); 17 Jul 2014 08:08:05 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 17 Jul 2014 08:08:05 +0000 Date: Thu, 17 Jul 2014 08:08:05 +0000 (UTC) From: "Rohith (JIRA)" To: mapreduce-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (MAPREDUCE-5910) MRAppMaster should handle Resync from RM instead of shutting down. MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/MAPREDUCE-5910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14064692#comment-14064692 ] Rohith commented on MAPREDUCE-5910: ----------------------------------- The test failure is same as MAPREDUCE-5973 > 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 (v6.2#6252)