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 A7E7D178F7 for ; Thu, 23 Apr 2015 23:45:41 +0000 (UTC) Received: (qmail 53710 invoked by uid 500); 23 Apr 2015 23:45:41 -0000 Delivered-To: apmail-hadoop-mapreduce-issues-archive@hadoop.apache.org Received: (qmail 53643 invoked by uid 500); 23 Apr 2015 23:45:41 -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 53629 invoked by uid 99); 23 Apr 2015 23:45:41 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 23 Apr 2015 23:45:41 +0000 Date: Thu, 23 Apr 2015 23:45:41 +0000 (UTC) From: "Vinod Kumar Vavilapalli (JIRA)" To: mapreduce-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (MAPREDUCE-6324) Uber jobs fail to update AMRM token when it rolls over 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-6324?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14510086#comment-14510086 ] Vinod Kumar Vavilapalli commented on MAPREDUCE-6324: ---------------------------------------------------- Looks good to me. One nit: testAllocResponseId is not really validating that responseIDs are changing? > Uber jobs fail to update AMRM token when it rolls over > ------------------------------------------------------ > > Key: MAPREDUCE-6324 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-6324 > Project: Hadoop Map/Reduce > Issue Type: Bug > Components: mr-am > Affects Versions: 2.6.0 > Reporter: Jason Lowe > Assignee: Jason Lowe > Priority: Blocker > Attachments: MAPREDUCE-6324.001.patch, MAPREDUCE-6324.002.patch > > > When the RM rolls a new AMRM master key the AMs are supposed to receive a new AMRM token on subsequent heartbeats between the time when the new key is rolled and when it is activated. This is not occurring for uber jobs. If the connection to the RM needs to be re-established after the new key is activated (e.g.: RM restart or network hiccup) then the uber job AM will be unable to reconnect to the RM. -- This message was sent by Atlassian JIRA (v6.3.4#6332)