[
https://issues.apache.org/jira/browse/IMPALA-9387?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17039596#comment-17039596
]
Tim Armstrong commented on IMPALA-9387:
---------------------------------------
I looked at this a while back too - I think it just goes through a lot of
permutations of permissions and it's fast enough when those are just in-memory,
but when adding each permission is an RPC, it's super-expensive. Ideally we'd
have some way to inject the permissions into the ranger plugin running locally
without having the modifying them on the server.
> AuthorizationStmtTest is very slow
> ----------------------------------
>
> Key: IMPALA-9387
> URL: https://issues.apache.org/jira/browse/IMPALA-9387
> Project: IMPALA
> Issue Type: Bug
> Components: Frontend
> Reporter: Csaba Ringhofer
> Priority: Major
> Attachments: AuthorizationStmtTest-Ranger-CPU-Sample.png,
> AuthorizationStmtTest-Ranger-cpu-profile.nps
>
>
> AuthorizationStmtTest takes around a hour to run in the jenkines runs I
> recently saw:
> 02:54:32.772 [INFO] Tests run: 58, Failures: 0, Errors: 0, Skipped: 0, Time
> elapsed: 3,436.751 s - in
> org.apache.impala.authorization.AuthorizationStmtTest
> This is extremely slow compared to other FE tests. I ran these tests with
> Sentry several times in the recent past, and they were below 1 min, so I
> think that Ranger tests are the culprit here.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
