+1. It can definitely be a pain for some admins to get new binaries like async-profiler installed across their machines outside of Ozone. How would we invoke the profiler after adding the dependency? I think the usual jcmd + pid option would still work, but it also looks like HBase added a Rest endpoint to do remote profiling. We could also consider adding an `ozone debug profile` CLI wrapper with common options for local or remote profiling.
Ethan On Sun, Jan 25, 2026 at 4:40 PM Wei-Chiu Chuang <[email protected]> wrote: > Didn't realize async profiler comes in maven dependency form as well. The > jar file itself is 890kb, not too terrible. Could be useful if we ship it > by default. > > ---------- Forwarded message --------- > From: Aman Poonia (Jira) <[email protected]> > Date: Sun, Jan 25, 2026 at 11:49 AM > Subject: [jira] [Created] (HBASE-29853) Move from async profiler binary to > a maven dependency > To: <[email protected]> > > > Aman Poonia created HBASE-29853: > ----------------------------------- > > Summary: Move from async profiler binary to a maven dependency > Key: HBASE-29853 > URL: https://issues.apache.org/jira/browse/HBASE-29853 > Project: HBase > Issue Type: Improvement > Affects Versions: 3.0.0-beta-1, 4.0.0-alpha-1, 2.6.4, 2.5.13 > Reporter: Aman Poonia > Assignee: Aman Poonia > Fix For: 2.7.0, 3.0.0-beta-2, 2.6.5, 2.5.14 > > > * *Velocity 2.4* disallows hyphens in variable names, requiring template > changes. > > * Updating the syntax now prepares us for upgrading to newer Velocity > versions. > > * This improves compatibility with plugins like > {*}maven-remote-resources-plugin{*}, which use the latest Velocity. > > * The current setup is pinned to {*}Velocity 1.7{*}, while the latest > version ({*}3.3.0{*}) runs on the *Velocity 2.x engine* by default. > > > > -- > This message was sent by Atlassian Jira > (v8.20.10#820010) >
