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 4EE031772F for ; Tue, 21 Apr 2015 21:31:04 +0000 (UTC) Received: (qmail 19831 invoked by uid 500); 21 Apr 2015 21:30:59 -0000 Delivered-To: apmail-hadoop-mapreduce-issues-archive@hadoop.apache.org Received: (qmail 19755 invoked by uid 500); 21 Apr 2015 21:30:59 -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 19743 invoked by uid 99); 21 Apr 2015 21:30:59 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 21 Apr 2015 21:30:59 +0000 Date: Tue, 21 Apr 2015 21:30:59 +0000 (UTC) From: "Jason Lowe (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=14505805#comment-14505805 ] Jason Lowe commented on MAPREDUCE-6324: --------------------------------------- Thanks for the review, Robert! Yes, this should have a unit test. Wanted to post a version without since I was able to manually test it with an uberized Oozie launcher job and verify it fixes the issue. I'm busy with a bunch of other stuff right now, but I'll try to take a crack at adding a unit test later this week. > 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 > > > 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)