Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: yarn-issues@hadoop.apache.org
Date: Wed, 23 Jul 2014 14:26:39 +0000 (UTC)
From: "Rohith (JIRA)" <jira@apache.org>
To: yarn-issues@hadoop.apache.org
Message-ID: <JIRA.12698541.1393895713567.29031.1406125599482@arcas>
In-Reply-To: <JIRA.12698541.1393895713567@arcas>
References: <JIRA.12698541.1393895713567@arcas>
Subject: [jira] [Commented] (YARN-1779) Handle AMRMTokens across RM failover
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Rohith commented on YARN-1779:
------------------------------

This is critical issue for work preserving restart feature. AM can not connect to new RM because of proxy object is cached and token service is overwritten.
One approach to solve this by cloning the token object and add token to UserGroupInformation. Sample like below
{code}
    for (Token<? extends TokenIdentifier> token : UserGroupInformation
        .getCurrentUser().getTokens()) {
      if (token.getKind().equals(AMRMTokenIdentifier.KIND_NAME)) {
        Token<? extends TokenIdentifier> specificToken = new Token(token);
        SecurityUtil.setTokenService(specificToken, resourceManagerAddress);
        UserGroupInformation.getCurrentUser().addToken(specificToken);
      }
    }
{code}
Does it make sense?

> Handle AMRMTokens across RM failover
> ------------------------------------
>
>                 Key: YARN-1779
>                 URL: https://issues.apache.org/jira/browse/YARN-1779
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: resourcemanager
>    Affects Versions: 2.3.0
>            Reporter: Karthik Kambatla
>            Priority: Blocker
>              Labels: ha
>
> Verify if AMRMTokens continue to work against RM failover. If not, we will have to do something along the lines of YARN-986. 


--
This message was sent by Atlassian JIRA
(v6.2#6252)