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 "Noemi Pap-Takacs (Jira)" <ji...@apache.org> on 2025/01/02 14:15:00 UTC
[jira] [Commented] (IMPALA-13616) Catalog timeline is missing from query profile in case of exception
[ https://issues.apache.org/jira/browse/IMPALA-13616?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17909311#comment-17909311 ]
Noemi Pap-Takacs commented on IMPALA-13616:
-------------------------------------------
I investigated this issue a bit further. The Catalog timeline is [added to the profile|https://github.com/apache/impala/blob/14b959d7bf7104d0172ce41df909fc0835067644/fe/src/main/java/org/apache/impala/service/CatalogOpExecutor.java#L7398] which is returned in the TCatalogUpdateResponse. In case of any exceptions, this path is not reached, therefore the timeline in the response thrift is not sent back to the Coordinator.
> Catalog timeline is missing from query profile in case of exception
> -------------------------------------------------------------------
>
> Key: IMPALA-13616
> URL: https://issues.apache.org/jira/browse/IMPALA-13616
> Project: IMPALA
> Issue Type: Improvement
> Components: Catalog
> Reporter: Noemi Pap-Takacs
> Assignee: Quanlong Huang
> Priority: Major
>
> The query profile contains a timeline for Catalog, Query Compilation and 'Query Timeline' under 'Errors'.
> This is an example of a successful DML operation.
> {noformat}
> Errors:
> Catalog Server Operation: 533.758ms
> - Got catalog version read lock: 2.746ms (2.746ms)
> - Got catalog version write lock and table write lock: 2.870ms (124.249us)
> - Executed Iceberg operation OPTIMIZE: 243.529ms (240.658ms)
> - Updated table properties: 248.339ms (4.810ms)
> - Got Metastore client: 470.222ms (221.882ms)
> (...)
> - Finished updateCatalog request: 533.758ms (428.717us)
> Query Compilation: 4s832ms
> - Metadata load started: 525.705us (525.705us)
> (..)
> - Distributed plan created: 4s617ms (11.530ms)
> - Planning finished: 4s832ms (215.162ms)
> Query Timeline: 7s653ms
> - Query submitted: 44.775us (44.775us)
> - Planning finished: 4s846ms (4s846ms)
> (..)
> - Request finished: 7s609ms (1.188us)
> - Unregister query: 7s653ms (43.672ms)
> - AdmissionControlTimeSinceLastUpdate: 86.000ms
> - ComputeScanRangeAssignmentTimer: 34.764us
> {noformat}
> However, if a runtime exception occurs, for example a ValidationException is thrown from Iceberg, the Catalog timeline disappears from the profile:
> {noformat}
> Errors:
> Query Compilation: 5s361ms
> - Metadata load started: 5.080ms (5.080ms)
> (...)
> {noformat}
>
> We should include the Catalog timeline in this case as well in order to gain observability.
--
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