You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-issues@hadoop.apache.org by "Wei-Chiu Chuang (Jira)" <ji...@apache.org> on 2022/01/06 09:58:00 UTC

[jira] [Updated] (HADOOP-18055) Async Profiler endpoint for Hadoop daemons

     [ https://issues.apache.org/jira/browse/HADOOP-18055?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Wei-Chiu Chuang updated HADOOP-18055:
-------------------------------------
    Fix Version/s: 3.4.0
       Resolution: Fixed
           Status: Resolved  (was: Patch Available)

Thanks [~vjasani]  for the PR and [~aajisaka]  for the review.

I am merging the PR. If any issues please file a follow up jira.

> Async Profiler endpoint for Hadoop daemons
> ------------------------------------------
>
>                 Key: HADOOP-18055
>                 URL: https://issues.apache.org/jira/browse/HADOOP-18055
>             Project: Hadoop Common
>          Issue Type: New Feature
>            Reporter: Viraj Jasani
>            Assignee: Viraj Jasani
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 3.4.0
>
>          Time Spent: 2h 40m
>  Remaining Estimate: 0h
>
> Async profiler ([https://github.com/jvm-profiling-tools/async-profiler]) is a low overhead sampling profiler for Java that does not suffer from Safepoint bias problem. It features HotSpot-specific APIs to collect stack traces and to track memory allocations. The profiler works with OpenJDK, Oracle JDK and other Java runtimes based on the HotSpot JVM.
> Async profiler can also profile heap allocations, lock contention, and HW performance counters in addition to CPU.
> We have an httpserver based servlet stack hence we can use HIVE-20202 as an implementation template to provide async profiler as servlet for Hadoop daemons. Ideally we achieve these requirements:
>  * Retrieve flamegraph SVG generated from latest profile trace.
>  * Online enable and disable of profiling activity. (async-profiler does not do instrumentation based profiling so this should not cause the code gen related perf problems of that other approach and can be safely toggled on and off while under production load.)
>  * CPU profiling.
>  * ALLOCATION profiling.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

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