Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[SPARK-2678][Core] Backport PR #1801 to branch-1.0 #1831

Closed
wants to merge 1 commit into from

Conversation

liancheng
Copy link
Contributor

Backport SPARK-2678 fix in PR #1801 to branch-1.0

@SparkQA
Copy link

SparkQA commented Aug 7, 2014

QA tests have started for PR 1831. This patch merges cleanly.
View progress: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/18115/consoleFull

@SparkQA
Copy link

SparkQA commented Aug 7, 2014

QA results for PR 1831:
- This patch PASSES unit tests.
- This patch merges cleanly
- This patch adds no public classes

For more information see test ouptut:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/18115/consoleFull

@pwendell
Copy link
Contributor

pwendell commented Aug 7, 2014

Thanks Cheng!

asfgit pushed a commit that referenced this pull request Aug 7, 2014
Backport  SPARK-2678 fix in PR #1801 to branch-1.0

Author: Cheng Lian <lian.cs.zju@gmail.com>

Closes #1831 from liancheng/spark-2678-for-1.0 and squashes the following commits:

cc59929 [Cheng Lian] Backported SPARK-2678 fix
@pwendell
Copy link
Contributor

pwendell commented Aug 8, 2014

@liancheng can you close this? I've merged it but things don't close properly in this case.

@liancheng liancheng closed this Aug 8, 2014
@liancheng liancheng deleted the spark-2678-for-1.0 branch September 24, 2014 00:08
viirya pushed a commit to viirya/spark-1 that referenced this pull request Oct 19, 2023
### What changes were proposed in this pull request?
This adds support for the async profiler to Spark 

### Why are the changes needed?
Profiling of JVM applications on a cluster is cumbersome and it can be complicated to save the output of the profiler especially if the cluster is on K8s where the executor pods are removed and any files saved to the local file system become inaccessible.
This feature makes it simple to turn profiling on/off, includes the jar/binaries needed for profiling,  and makes it simple to save output to an HDFS location.

### Does this PR introduce _any_ user-facing change?
This PR introduces three new configuration parameters. These are described in the documentation.

### How was this patch tested?
Manually on an EKS cluster
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants