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 28008D2BE for ; Sat, 22 Dec 2012 00:29:14 +0000 (UTC) Received: (qmail 94259 invoked by uid 500); 22 Dec 2012 00:29:14 -0000 Delivered-To: apmail-hadoop-yarn-issues-archive@hadoop.apache.org Received: (qmail 94225 invoked by uid 500); 22 Dec 2012 00:29:14 -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 94216 invoked by uid 99); 22 Dec 2012 00:29:14 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 22 Dec 2012 00:29:14 +0000 Date: Sat, 22 Dec 2012 00:29:13 +0000 (UTC) From: "Karthik Kambatla (JIRA)" To: yarn-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (YARN-279) Generalize RM token management 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-279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13538573#comment-13538573 ] Karthik Kambatla commented on YARN-279: --------------------------------------- If we are abstracting out token management from RM, would it make sense to push it all the way down to common and use some of the existing token-management code (renewal etc.)? > Generalize RM token management > ------------------------------ > > Key: YARN-279 > URL: https://issues.apache.org/jira/browse/YARN-279 > Project: Hadoop YARN > Issue Type: Improvement > Components: resourcemanager > Affects Versions: 3.0.0, 2.0.0-alpha, 0.23.5 > Reporter: Daryn Sharp > > Token renewal/cancelation in the RM presents challenges to support arbitrary tokens. The RM's CLASSPATH is currently required to have token renewer classes and all associated classes for the project's client. The logistics of having installs on the RM of all hadoop projects that submit jobs - just to support client connections to renew/cancel tokens - are untenable. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira