[
https://issues.apache.org/jira/browse/IMPALA-6663?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17050543#comment-17050543
]
ASF subversion and git services commented on IMPALA-6663:
---------------------------------------------------------
Commit 2b173dd41bcce1d68109c3559f9b0a7ec0d8a90f in impala's branch
refs/heads/master from Tamas Mate
[ https://gitbox.apache.org/repos/asf?p=impala.git;h=2b173dd ]
IMPALA-6663: Expose current DDL metrics on WebUI
This change adds a new '/operations' tab to the Catalog WebUI. On this
page the users can see two summary tables, the first report is based on
how many catalog operations are running and which tables are involved.
The second report shows the number of catalog operations on table level.
A new 'monitor' package is created to collect the monitoring classes.
Each DDL/FinalizeDML/ResetMetada request get a class with common base
class. The output of these classes are summarized and can be accessed
with a new JNI call.
A screenshot of the new '/operations' page can be found in the Jira.
Testing:
Unit tests were added to test the counters and a web server test to
verify the availability of the page.
Change-Id: I0ed76f134bad6d3b3d4dce132365a53a01e9512a
Reviewed-on: http://gerrit.cloudera.org:8080/13806
Reviewed-by: Impala Public Jenkins <[email protected]>
Tested-by: Impala Public Jenkins <[email protected]>
> 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
> Components: Catalog
> Affects Versions: Impala 2.12.0
> Reporter: Bharath Vissapragada
> Assignee: Tamas Mate
> Priority: Major
> Labels: observability, ramp-up, supportability
> Attachments: catalog_new_operations_page.png,
> catalog_new_operations_page_v2.png, catalog_page_new_bottom_v2.png,
> catalog_page_new_top.png, catalog_page_original.png
>
>
> 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
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
