[ 
https://issues.apache.org/jira/browse/HBASE-21926?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16791074#comment-16791074
 ] 

Hadoop QA commented on HBASE-21926:
-----------------------------------

| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue}  0m  
0s{color} | {color:blue} Docker mode activated. {color} |
| {color:red}-1{color} | {color:red} docker {color} | {color:red}  4m 
30s{color} | {color:red} Docker failed to build yetus/hbase:61288f8. {color} |
\\
\\
|| Subsystem || Report/Notes ||
| JIRA Issue | HBASE-21926 |
| JIRA Patch URL | 
https://issues.apache.org/jira/secure/attachment/12962212/HBASE-21926-branch-1.patch
 |
| Console output | 
https://builds.apache.org/job/PreCommit-HBASE-Build/16361/console |
| Powered by | Apache Yetus 0.8.0   http://yetus.apache.org |


This message was automatically generated.



> Profiler servlet
> ----------------
>
>                 Key: HBASE-21926
>                 URL: https://issues.apache.org/jira/browse/HBASE-21926
>             Project: HBase
>          Issue Type: New Feature
>          Components: master, Operability, regionserver
>            Reporter: Andrew Purtell
>            Assignee: Andrew Purtell
>            Priority: Major
>             Fix For: 3.0.0, 1.6.0, 2.3.0
>
>         Attachments: 1.png, 2.png, 3.png, 4.png, HBASE-21926-branch-1.patch, 
> HBASE-21926.patch
>
>
> HIVE-20202 describes how Hive added a web endpoint for online in production 
> profiling based on async-profiler. The endpoint was added as a servlet to 
> httpserver and supports retrieval of flamegraphs compiled from the profiler 
> trace. Async profiler 
> ([https://github.com/jvm-profiling-tools/async-profiler] ) can also profile 
> heap allocations, lock contention, and HW performance counters in addition to 
> CPU.
> The profiling overhead is pretty low and is safe to run in production. The 
> async-profiler project measured and describes CPU and memory overheads on 
> these issues: 
> [https://github.com/jvm-profiling-tools/async-profiler/issues/14] and 
> [https://github.com/jvm-profiling-tools/async-profiler/issues/131] 
> We have an httpserver based servlet stack so we can use HIVE-20202 as an 
> implementation template for a similar feature for HBase 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
(v7.6.3#76005)

Reply via email to