You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@impala.apache.org by "bharath v (JIRA)" <ji...@apache.org> on 2018/03/14 18:55:00 UTC
[jira] [Created] (IMPALA-6663) Expose current DDL metrics (grouped
by type) in the Catalog web UI
bharath v created IMPALA-6663:
---------------------------------
Summary: Expose current DDL metrics (grouped by type) in the Catalog web UI
Key: IMPALA-6663
URL: https://issues.apache.org/jira/browse/IMPALA-6663
Project: IMPALA
Issue Type: Improvement
Affects Versions: Impala 2.12.0
Reporter: bharath v
It helps if the catalog server can expose currently running (counts) DDL and RESET_METADATA requests via the web UI metrics. From an observability/supportability point of view, these numbers help reason about the Cluster behavior during Catalog heavy load or in situations where Catalog server is the bottleneck
Following are some of the interesting ones that I think are interesting.
{noformat}
enum TDdlType {
ALTER_TABLE,
ALTER_VIEW,
CREATE_DATABASE,
CREATE_TABLE,
CREATE_TABLE_AS_SELECT,
CREATE_TABLE_LIKE,
CREATE_VIEW,
CREATE_FUNCTION,
COMPUTE_STATS,
DROP_DATABASE,
DROP_TABLE,
DROP_VIEW,
DROP_FUNCTION,
CREATE_DATA_SOURCE,
DROP_DATA_SOURCE,
DROP_STATS,
CREATE_ROLE,
DROP_ROLE,
GRANT_ROLE,
REVOKE_ROLE,
GRANT_PRIVILEGE,
REVOKE_PRIVILEGE,
TRUNCATE_TABLE,
}
TCatalogOpType.RESET_METADATA
TStmtType.DML
{noformat}
This should be based on the metrics framework added in IMPALA-4886.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)