[
https://issues.apache.org/jira/browse/SPARK-60612?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Cheng Pan updated SPARK-60612:
------------------------------
Affects Version/s: 4.4.0
(was: 5.0.0)
> Remove unnecessary dump execution in SparkAsyncProfiler
> -------------------------------------------------------
>
> Key: SPARK-60612
> URL: https://issues.apache.org/jira/browse/SPARK-60612
> Project: Spark
> Issue Type: Improvement
> Components: Spark Core
> Affects Versions: 4.4.0
> Reporter: Zhen Wang
> Assignee: Zhen Wang
> Priority: Minor
> Labels: pull-request-available
>
> SparkAsyncProfiler.writeChunk executes {{dump}} immediately after {{stop}},
> but this call has no effect for JFR output.
> In async-profiler:
> *
> [Profiler::stop|https://github.com/async-profiler/async-profiler/blob/v4.5/src/profiler.cpp#L1096]
> stops the JFR recording and sets {{_state = IDLE}}.
> *
> [Profiler::dump|https://github.com/async-profiler/async-profiler/blob/v4.5/src/profiler.cpp#L1144-L1150]
> only flushes JFR data when {{_state == RUNNING}}.
> Since the profiler is already in the {{IDLE}} state, the subsequent {{dump}}
> does nothing.
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
