[
https://issues.apache.org/jira/browse/YARN-7889?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16353154#comment-16353154
]
Jian He commented on YARN-7889:
-------------------------------
Patch, lgtm,
One side issue noticed is that, till now, the client library (YarnClient,
AMRMClient) YARN exposes have builtin retry, and applications may assume that
the retry is handled automatically. But the ApiServiceClient doesn't have retry
built-in, this may be a caveat for applications later. I think we can deal with
this later when requests come.
> Missing kerberos token when check for RM REST API availability
> --------------------------------------------------------------
>
> Key: YARN-7889
> URL: https://issues.apache.org/jira/browse/YARN-7889
> Project: Hadoop YARN
> Issue Type: Bug
> Components: yarn-native-services
> Affects Versions: 3.1.0
> Reporter: Eric Yang
> Assignee: Eric Yang
> Priority: Major
> Attachments: YARN-7889.001.patch, YARN-7889.002.patch
>
>
> When checking for which resource manager can be used for REST API request,
> client side must send kerberos token to REST API end point. The checking
> mechanism is currently missing the kerberos token.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
