|
29 | 29 |
|
30 | 30 | == Background |
31 | 31 |
|
32 | | -HBASE-21926 introduced a new servlet that supports integrated profiling via async-profiler. |
| 32 | +https://issues.apache.org/jira/browse/HBASE-21926[HBASE-21926] introduced a new servlet that |
| 33 | +supports integrated, on-demand profiling via the |
| 34 | +https://github.com/jvm-profiling-tools/async-profiler[Async Profiler] project. |
33 | 35 |
|
34 | 36 | == Prerequisites |
35 | 37 |
|
36 | | -Go to https://github.com/jvm-profiling-tools/async-profiler, download a release appropriate for your platform, and install on every cluster host. |
37 | | -If 4.6 or later linux, be sure to set proc variables as per 'Basic Usage' section in the |
38 | | -<a href="https://github.com/jvm-profiling-tools/async-profiler">Async Profiler Home Page</a> |
39 | | -(Not doing this will draw you diagrams with no content). |
| 38 | +Go to the https://github.com/jvm-profiling-tools/async-profiler[Async Profiler Home Page], download |
| 39 | +a release appropriate for your platform, and install on every cluster host. If running a Linux |
| 40 | +kernel v4.6 or later, be sure to set proc variables as per the |
| 41 | +https://github.com/jvm-profiling-tools/async-profiler#basic-usage[Basic Usage] section. Not doing |
| 42 | +so will result in flame graphs that contain no content. |
40 | 43 |
|
41 | | -Set `ASYNC_PROFILER_HOME` in the environment (put it in hbase-env.sh) to the root directory of the async-profiler install location, or pass it on the HBase daemon's command line as a system property as `-Dasync.profiler.home=/path/to/async-profiler`. |
| 44 | +Set `ASYNC_PROFILER_HOME` in the environment (put it in hbase-env.sh) to the root directory of the |
| 45 | +async-profiler install location, or pass it on the HBase daemon's command line as a system property |
| 46 | +as `-Dasync.profiler.home=/path/to/async-profiler`. |
42 | 47 |
|
43 | 48 | == Usage |
44 | 49 |
|
45 | | -Once the prerequisites are satisfied, access to async-profiler is available by way of the HBase UI or direct interaction with the infoserver. |
| 50 | +Once the prerequisites are satisfied, access to async-profiler is available by way of the HBase UI |
| 51 | +or direct interaction with the infoserver. |
46 | 52 |
|
47 | 53 | Examples: |
48 | 54 |
|
|
0 commit comments