Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: yarn-issues@hadoop.apache.org
Date: Wed, 19 Jun 2013 04:25:21 +0000 (UTC)
From: "Omkar Vinit Joshi (JIRA)" <jira@apache.org>
To: yarn-issues@hadoop.apache.org
Message-ID: <JIRA.12653606.1371600114379.138144.1371615921751@arcas>
In-Reply-To: <JIRA.12653606.1371600114379@arcas>
References: <JIRA.12653606.1371600114379@arcas>
Subject: [jira] [Commented] (YARN-851) Share NMTokens using NMTokenCache
 (api-based) instead of memory based approach which is used currently.
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/YARN-851?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13687592#comment-13687592 ] 

Omkar Vinit Joshi commented on YARN-851:
----------------------------------------

static NMTokenCache is created which will be one per jvm. RMContainerAllocator/AMRMClient will put newly received tokens in it. NMClient /ContainerManagementProtocolProxy which needs NMToken for creating authenticated connection with NM will pick up token from here.
                
> Share NMTokens using NMTokenCache (api-based) instead of memory based approach which is used currently.
> -------------------------------------------------------------------------------------------------------
>
>                 Key: YARN-851
>                 URL: https://issues.apache.org/jira/browse/YARN-851
>             Project: Hadoop YARN
>          Issue Type: Bug
>            Reporter: Omkar Vinit Joshi
>            Assignee: Omkar Vinit Joshi
>         Attachments: YARN-851-20130618.patch
>
>
> It is a follow up ticket for YARN-694. Changing the way NMTokens are shared.

--
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