[
https://issues.apache.org/jira/browse/YARN-8589?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16773758#comment-16773758
]
Prabhu Joseph commented on YARN-8589:
-------------------------------------
[~Rakesh_Shah] The getEntities api (Tez UI) will get set of entities matching
the query params and the ones which requested user has access. The getEntities
will be slow when checkAccess has to happen for every entity. Tez UI to view
list of apps and app details will be slower due to this.
Simple testcase which does n putEntities and do getEntities with acl enabled,
getEntities will be very slow comparing with acl not enabled or for admin user.
We can test with MapReduce also - mapreduce jobs , RM putEntities and use below
api to getEntities.
curl --negotiate -u :
"http://prabhuzeppelin3.openstacklocal:8188/ws/v1/timeline/entities";
> ATS TimelineACLsManager checkAccess is slow
> -------------------------------------------
>
> Key: YARN-8589
> URL: https://issues.apache.org/jira/browse/YARN-8589
> Project: Hadoop YARN
> Issue Type: Bug
> Components: timelineserver
> Affects Versions: 2.7.3
> Reporter: Prabhu Joseph
> Priority: Major
>
> ATS rest api is very slow when there are more than 1lakh entries if
> yarn.acl.enable is set to true as TimelineACLsManager has to check access for
> every entries. We can;t disable yarn.acl.enable as all the YARN ACLs uses the
> same config. We can have a separate config to provide read access to the ATS
> Entries.
> {code}
> curl http://<ATS Server>:8188/ws/v1/timeline/HIVE_QUERY_ID
> {code}
--
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
