Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Date: Thu, 18 May 2017 01:04:04 +0000 (UTC)
From: "Robert Kanter (JIRA)" <jira@apache.org>
To: yarn-issues@hadoop.apache.org
Message-ID: <JIRA.13072093.1494870641000.236217.1495069444914@Atlassian.JIRA>
In-Reply-To: <JIRA.13072093.1494870641000@Atlassian.JIRA>
References: <JIRA.13072093.1494870641000@Atlassian.JIRA> <JIRA.13072093.1494870641807@jira-lw-us.apache.org>
Subject: [jira] [Updated] (YARN-6602) Impersonation does not work if standby
 RM is contacted first
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Thu, 18 May 2017 01:04:09 -0000


     [ https://issues.apache.org/jira/browse/YARN-6602?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Robert Kanter updated YARN-6602:
--------------------------------
    Attachment: YARN-6602.002.patch

The 002 patch
- Fixes the (relevant) checkstyle warnings, including making {{RMProxy.user}} private.

> Impersonation does not work if standby RM is contacted first
> ------------------------------------------------------------
>
>                 Key: YARN-6602
>                 URL: https://issues.apache.org/jira/browse/YARN-6602
>             Project: Hadoop YARN
>          Issue Type: Bug
>          Components: client
>    Affects Versions: 3.0.0-alpha3
>            Reporter: Robert Kanter
>            Assignee: Robert Kanter
>            Priority: Blocker
>         Attachments: YARN-6602.001.patch, YARN-6602.002.patch
>
>
> When RM HA is enabled, impersonation does not work correctly if the Yarn Client connects to the standby RM first.  When this happens, the impersonation is "lost" and the client does things on behalf of the impersonator user.  We saw this with the OOZIE-1770 Oozie on Yarn feature.
> I need to investigate this some more, but it appears to be related to delegation tokens.  When this issue occurs, the tokens have the owner as "oozie" instead of the actual user.  On a hunch, we found a workaround that explicitly adding a correct RM HA delegation token fixes the problem:
> {code:java}
> org.apache.hadoop.yarn.api.records.Token token = yarnClient.getRMDelegationToken(ClientRMProxy.getRMDelegationTokenService(conf));
> org.apache.hadoop.security.token.Token token2 = new org.apache.hadoop.security.token.Token(token.getIdentifier().array(), token.getPassword().array(), new Text(token.getKind()), new Text(token.getService()));
> UserGroupInformation.getCurrentUser().addToken(token2);
> {code}


--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org