Details
-
New Feature
-
Status: Resolved
-
Critical
-
Resolution: Fixed
-
None
-
ghx-label-9
Description
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.
- 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
Attachments
Attachments
Issue Links
- causes
-
IMPALA-12687 Key conflicts in catalog inFlightOperations when catalog RPC retries
- Resolved
- is related to
-
IMPALA-12778 Catalog operations page is showing UTC time strings
- Resolved
-
IMPALA-6557 Show details of recent topic delta update
- Open
- relates to
-
IMPALA-7959 Trace and visualize concurrent Catalog operations
- Open
-
IMPALA-6663 Expose current DDL metrics (grouped by type) in the Catalog web UI
- Resolved