You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues-all@impala.apache.org by "ASF subversion and git services (Jira)" <ji...@apache.org> on 2022/07/19 11:02:00 UTC
[jira] [Commented] (IMPALA-8443) Record time spent in authorization in the runtime profile
[ https://issues.apache.org/jira/browse/IMPALA-8443?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17568475#comment-17568475 ]
ASF subversion and git services commented on IMPALA-8443:
---------------------------------------------------------
Commit 733c950dafd91460e06122b231dc4a4371e0fe85 in impala's branch refs/heads/master from stiga-huang
[ https://gitbox.apache.org/repos/asf?p=impala.git;h=733c950da ]
IMPALA-11406: Fix incorrect duration log for authorization
IMPALA-8443 extends EventSequence.markEvent() to return the duration
between the last and the current event. However, the duration is
calculated using the start time, not the last time it's invoked, which
causes misleading time in logs of "Authorization check took n ms".
This fixes the bug and also adds a log for the analysis duration.
Change-Id: I8b665f1b4ac86577711598ce9d845cf82fedbcd7
Reviewed-on: http://gerrit.cloudera.org:8080/18682
Reviewed-by: Impala Public Jenkins <im...@cloudera.com>
Tested-by: Impala Public Jenkins <im...@cloudera.com>
> Record time spent in authorization in the runtime profile
> ---------------------------------------------------------
>
> Key: IMPALA-8443
> URL: https://issues.apache.org/jira/browse/IMPALA-8443
> Project: IMPALA
> Issue Type: Improvement
> Components: Frontend
> Affects Versions: Impala 3.2.0
> Reporter: Bharath Vissapragada
> Assignee: Tamas Mate
> Priority: Major
> Labels: newbie, supportability
> Fix For: Impala 3.3.0
>
>
> Authorization is done as a part of analysis. It helps to have the time spent in authorization recorded as a part of the query profile timeline. Something like as follows. Helps to debug issues when bottleneck is in authorization.
> {noformat}
> Query Compilation
> Metadata load started: 4ms (4559114)
> Metadata load finished. loaded-tables=1/2 load-requests=1 catalog-updates=3: 2.60s (2599515306)
> Authorization finished (Ranger|Sentry): xxxxx ++++++++++
> Analysis finished: 1.9m (113860685080)
> Value transfer graph computed: 1.9m (113863830763)
> Single node plan created: 1.9m (116880551103)
> Runtime filters computed: 1.9m (116880914428)
> Distributed plan created: 1.9m (116882951541)
> Lineage info computed: 1.9m (116884735701)
> Planning finished: 1.9m (116900204008)
> Planning finished: 1.9m (116900208344)
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-all-unsubscribe@impala.apache.org
For additional commands, e-mail: issues-all-help@impala.apache.org