parthchandra commented on code in PR #49492:
URL: https://github.com/apache/spark/pull/49492#discussion_r1917373680
##########
connector/profiler/README.md:
##########
@@ -39,7 +39,7 @@ For more information on async_profiler see the [Async
Profiler Manual](https://k
To enable code profiling, first enable the code profiling plugin via
```
-spark.plugins=org.apache.spark.executor.profiler.ExecutorProfilerPlugin
+spark.plugins=org.apache.spark.profiler.ProfilerPlugin
Review Comment:
Do we need to document anywhere that the name of the plugin and the related
options have changed?
##########
connector/profiler/README.md:
##########
@@ -60,36 +68,28 @@ Then enable the profiling in the configuration.
<td>4.0.0</td>
</tr>
<tr>
- <td><code>spark.executor.profiling.localDir</code></td>
+ <td><code>spark.profiler.localDir</code></td>
<td><code>.</code> i.e. the executor's working dir</td>
<td>
The local directory in the executor container to write the jfr files to. If
not specified the file will be written to the executor's working directory.
Users should ensure there is sufficient disk space available on the system as
running out of space may result in corrupt jfr file and even cause jobs to fail
on systems like K8s.
</td>
<td>4.0.0</td>
</tr>
<tr>
- <td><code>spark.executor.profiling.options</code></td>
+ <td><code>spark.profiler.asyncProfiler.args</code></td>
<td>event=wall,interval=10ms,alloc=2m,lock=10ms,chunktime=300s</td>
<td>
- Options to pass to the profiler. Detailed options are documented in the
comments here:
+ Arguments to pass to the Async Profiler. Detailed options are documented
in the comments here:
Review Comment:
+1
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
