You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues-all@impala.apache.org by "Zoltán Borók-Nagy (Jira)" <ji...@apache.org> on 2022/11/04 21:32:00 UTC

[jira] [Created] (IMPALA-11705) Add Java profiler endpoint to Impala web UI

Zoltán Borók-Nagy created IMPALA-11705:
------------------------------------------

             Summary: Add Java profiler endpoint to Impala web UI
                 Key: IMPALA-11705
                 URL: https://issues.apache.org/jira/browse/IMPALA-11705
             Project: IMPALA
          Issue Type: Improvement
            Reporter: Zoltán Borók-Nagy


Hive and Ozone adds profiler endpoints to their web servers.
They use the async profiler: https://github.com/jvm-profiling-tools/async-profiler

Profiling the Java components (Frontend, CatalogD) could be very easy with this approach.
The users would just navigate to the web UI, provide some parameters, then they would get the results in e.g. flamegraphs.

async-profiler have support for these:
* CPU profiling
* Allocation profiling
* Lock contentions
* Java method profiling

Using the async-profiler is extremely simple. And based on the other Jiras "the profiling overhead is pretty low and is safe to run on production".

Related Jiras:
* HIVE-20202
* HDDS-1116
* HDDS-1117

They also add the async profiler to their docker images:
https://github.com/apache/hadoop/pull/492/files

So we could use this even in containerized environments.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

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