[
https://issues.apache.org/jira/browse/HBASE-25149?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nick Dimiduk updated HBASE-25149:
---------------------------------
Description: When the profiling servlet runs async-profiler when the output
path ({{/tmp/prof-output}}) doesn't exist or isn't writable by the {{hbase}}
process, it will sit in a refresh loop indefinitely. The servlet should check
that the output path is writable, or even make an attempt to create the output
directory, and inform the user of the situation, rather than attempting and
silently failing to generate the flame graph. (was: When the profiling servlet
runs async-profiler when the output path ({{/tmp/prof-output}} doesn't exist or
isn't writable by the {{hbase}} process, it will sit in a refresh loop
indefinitely. The servlet should check that the output path is writable, or
even make an attempt to create the output directory, and inform the user of the
situation, rather than attempting and silently failing to generate the flame
graph.)
> Profiling servlet ensure output directory exists and is writable
> ----------------------------------------------------------------
>
> Key: HBASE-25149
> URL: https://issues.apache.org/jira/browse/HBASE-25149
> Project: HBase
> Issue Type: Bug
> Components: Performance
> Affects Versions: 2.3.0
> Reporter: Nick Dimiduk
> Priority: Minor
>
> When the profiling servlet runs async-profiler when the output path
> ({{/tmp/prof-output}}) doesn't exist or isn't writable by the {{hbase}}
> process, it will sit in a refresh loop indefinitely. The servlet should
> check that the output path is writable, or even make an attempt to create the
> output directory, and inform the user of the situation, rather than
> attempting and silently failing to generate the flame graph.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
