[
https://issues.apache.org/jira/browse/HBASE-29853?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18075180#comment-18075180
]
Andrew Kyle Purtell commented on HBASE-29853:
---------------------------------------------
The availability of a profiler on the server side can be a security risk and so
some (or many) may opt not to place one there. This change does not gracefully
handle the absence of the profiler nor make its deployment optional.
> 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
> Priority: Minor
> Labels: pull-request-available
>
> Currently we set ASYNC_PROFILER binary path and then use that binary to
> execute in a shell. Instead we can use below maven dependency
> {code:java}
> https://mvnrepository.com/artifact/tools.profiler/async-profiler -->
> <dependency>
> <groupId>tools.profiler</groupId>
> <artifactId>async-profiler</artifactId>
> <version>2.9</version>
> <scope>compile</scope>
> </dependency>{code}
> This will make it easier to use async profiler everywhere in hbase.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
