[
https://issues.apache.org/jira/browse/YARN-4126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15595010#comment-15595010
]
Jason Lowe commented on YARN-4126:
----------------------------------
I'm just going off of [~rkanter]'s post in the yarn-dev mailing list that says
this change breaks Oozie in non-secure cluster deployments. If Oozie was
(mostly?) working in a non-secure setup before and now can't submit any kind of
workflow successfully after this change then it seems like we need to revert
this or risk breaking a major piece of functionality in the Hadoop stack when
people upgrade to 2.8.
> RM should not issue delegation tokens in unsecure mode
> ------------------------------------------------------
>
> Key: YARN-4126
> URL: https://issues.apache.org/jira/browse/YARN-4126
> Project: Hadoop YARN
> Issue Type: Bug
> Reporter: Jian He
> Assignee: Bibin A Chundatt
> Fix For: 2.8.0, 3.0.0-alpha1
>
> Attachments: 0001-YARN-4126.patch, 0002-YARN-4126.patch,
> 0003-YARN-4126.patch, 0004-YARN-4126.patch, 0005-YARN-4126.patch,
> 0006-YARN-4126.patch
>
>
> ClientRMService#getDelegationToken is currently returning a delegation token
> in insecure mode. We should not return the token if it's in insecure mode.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
