From yarn-issues-return-33564-apmail-hadoop-yarn-issues-archive=hadoop.apache.org@hadoop.apache.org Wed Aug 13 16:32:13 2014 Return-Path: X-Original-To: apmail-hadoop-yarn-issues-archive@minotaur.apache.org Delivered-To: apmail-hadoop-yarn-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 2A4A811471 for ; Wed, 13 Aug 2014 16:32:13 +0000 (UTC) Received: (qmail 37883 invoked by uid 500); 13 Aug 2014 16:32:12 -0000 Delivered-To: apmail-hadoop-yarn-issues-archive@hadoop.apache.org Received: (qmail 37840 invoked by uid 500); 13 Aug 2014 16:32:12 -0000 Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: yarn-issues@hadoop.apache.org Delivered-To: mailing list yarn-issues@hadoop.apache.org Received: (qmail 37828 invoked by uid 99); 13 Aug 2014 16:32:12 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 13 Aug 2014 16:32:12 +0000 Date: Wed, 13 Aug 2014 16:32:12 +0000 (UTC) From: "Hitesh Shah (JIRA)" To: yarn-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (YARN-1915) ClientToAMTokenMasterKey should be provided to AM at launch time 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/YARN-1915?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14095671#comment-14095671 ] Hitesh Shah commented on YARN-1915: ----------------------------------- [~jlowe] [~daryn] Was there a reason for not sending in the secret to the AM via its env when it launches? I am assuming this is to not have all the AMs to change to handle this? Wouldn't that be a more effective solution as compared to use of a timer ( which in practice would work ) but is still reliant upon the AM receiving the secret from the RM within the time window before the client does. > ClientToAMTokenMasterKey should be provided to AM at launch time > ---------------------------------------------------------------- > > Key: YARN-1915 > URL: https://issues.apache.org/jira/browse/YARN-1915 > Project: Hadoop YARN > Issue Type: Sub-task > Affects Versions: 2.2.0 > Reporter: Hitesh Shah > Assignee: Jason Lowe > Priority: Critical > Attachments: YARN-1915.patch, YARN-1915v2.patch > > > Currently, the AM receives the key as part of registration. This introduces a race where a client can connect to the AM when the AM has not received the key. > Current Flow: > 1) AM needs to start the client listening service in order to get host:port and send it to the RM as part of registration > 2) RM gets the port info in register() and transitions the app to RUNNING. Responds back with client secret to AM. > 3) User asks RM for client token. Gets it and pings the AM. AM hasn't received client secret from RM and so RPC itself rejects the request. -- This message was sent by Atlassian JIRA (v6.2#6252)