[
https://issues.apache.org/jira/browse/YARN-8869?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16650432#comment-16650432
]
Hudson commented on YARN-8869:
------------------------------
SUCCESS: Integrated in Jenkins build Hadoop-trunk-Commit #15215 (See
[https://builds.apache.org/job/Hadoop-trunk-Commit/15215/])
YARN-8869. YARN Service Client might not work correctly with RM REST API
(sunilg: rev fa94d370b6e3cba9c7560c09b517583e6652f103)
* (edit)
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-applications/hadoop-yarn-services/hadoop-yarn-services-api/src/main/java/org/apache/hadoop/yarn/service/client/ApiServiceClient.java
* (edit)
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-applications/hadoop-yarn-services/hadoop-yarn-services-api/src/test/java/org/apache/hadoop/yarn/service/client/TestSecureApiServiceClient.java
> YARN Service Client might not work correctly with RM REST API for Kerberos
> authentication
> -----------------------------------------------------------------------------------------
>
> Key: YARN-8869
> URL: https://issues.apache.org/jira/browse/YARN-8869
> Project: Hadoop YARN
> Issue Type: Bug
> Affects Versions: 3.1.0, 3.2.0, 3.1.1
> Reporter: Eric Yang
> Assignee: Eric Yang
> Priority: Blocker
> Fix For: 3.2.0, 3.1.2, 3.3.0
>
> Attachments: YARN-8869.001.patch, YARN-8869.002.patch,
> YARN-8869.003.patch, YARN-8869.004.patch
>
>
> ApiServiceClient uses WebResource instead of Builder to pass Kerberos
> authorization header. This may not work sometimes, and it is because
> WebResource.header() could be bind mashed new Builder instance in some
> condition. This article explained the details:
> https://juristr.com/blog/2015/05/jersey-webresource-ignores-headers/
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
