[
https://issues.apache.org/jira/browse/IMPALA-9118?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Abhishek Rawat updated IMPALA-9118:
-----------------------------------
Priority: Critical (was: Major)
> 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
> Assignee: Quanlong Huang
> Priority: Critical
> Labels: observability, supportability
> Attachments: Selection_082.png
>
>
> 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.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
