[jira] [Commented] (IMPALA-9118) Add debug page for in-flight DDLs in catalogd

["Quanlong Huang (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/IMPALA-9118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17380907#comment-17380907 ] 

Quanlong Huang commented on IMPALA-9118:
----------------------------------------

Some requests are added in IMPALA-6663.

> Add debug page for in-flight DDLs in catalogd
> ---------------------------------------------
>
>                 Key: IMPALA-9118
>                 URL: https://issues.apache.org/jira/browse/IMPALA-9118
>             Project: IMPALA
>          Issue Type: New Feature
>          Components: Catalog
>            Reporter: Quanlong Huang
>            Priority: Major
>              Labels: observability, supportability
>
> In a busy cluster, it's possible that many DDL/DML queries keep in the CREATED state for several minutes. Especially when using with sync_ddl=true, tens of minutes are also possible. They may be waiting for the ExecDdl RPC to catalogd to finish.
> It'd be helpful for debugging DDL/DML hangs if we can show the in-flight DDLs in catalogd. I think the following fields are important:
>  * thread id
>  * coordinator
>  * db name / table name
>  * ddl type, e.g. AddPartition, DropTable, CreateTable, etc. More types [here|https://github.com/apache/impala/blob/3.3.0/common/thrift/JniCatalog.thrift#L31].
>  * last event, e.g. waiting for table lock, got table lock, loading file metadata, waiting for sync ddl version etc.
>  * start time
>  * time elapsed
>  * (optional) params link to show the TDdlExecRequest in json format
> It'd be better to also include running REFRESH/INVALIDATE METADATA commands 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-all-unsubscribe@impala.apache.org
For additional commands, e-mail: issues-all-help@impala.apache.org