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

fix spark-6033, clarify the spark.worker.cleanup behavior in standalone mode #4803

Closed
wants to merge 1 commit into from
Closed

Conversation

hseagle
Copy link

@hseagle hseagle commented Feb 27, 2015

jira case spark-6033 https://issues.apache.org/jira/browse/SPARK-6033

In standalone deploy mode, the cleanup will only remove the stopped application's directories.

The original description about the cleanup behavior is incorrect.

@AmplabJenkins
Copy link

Can one of the admins verify this patch?

@@ -222,8 +222,7 @@ SPARK_WORKER_OPTS supports the following system properties:
<td>false</td>
<td>
Enable periodic cleanup of worker / application directories. Note that this only affects standalone
mode, as YARN works differently. Applications directories are cleaned up regardless of whether
the application is still running.
mode, as YARN works differently. Only the stopped applications directories are cleaned up.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Only the directories of stopped applications are cleaned up.

I will fix this myself when I merge

@andrewor14
Copy link
Contributor

LGTM merging into master and 1.3 and all the way back to 1.0. Thanks.

asfgit pushed a commit that referenced this pull request Feb 27, 2015
…ne mode

jira case spark-6033 https://issues.apache.org/jira/browse/SPARK-6033

In standalone deploy mode, the cleanup will only remove the stopped application's directories.

The original description about the cleanup behavior is incorrect.

Author: 许鹏 <peng.xu@fraudmetrix.cn>

Closes #4803 from hseagle/spark-6033 and squashes the following commits:

927a6a0 [许鹏] fix the incorrect description about the spark.worker.cleanup in standalone mode

(cherry picked from commit 0375a41)
Signed-off-by: Andrew Or <andrew@databricks.com>
@asfgit asfgit closed this in 0375a41 Feb 27, 2015
asfgit pushed a commit that referenced this pull request Feb 27, 2015
…ne mode

jira case spark-6033 https://issues.apache.org/jira/browse/SPARK-6033

In standalone deploy mode, the cleanup will only remove the stopped application's directories.

The original description about the cleanup behavior is incorrect.

Author: 许鹏 <peng.xu@fraudmetrix.cn>

Closes #4803 from hseagle/spark-6033 and squashes the following commits:

927a6a0 [许鹏] fix the incorrect description about the spark.worker.cleanup in standalone mode
asfgit pushed a commit that referenced this pull request Feb 27, 2015
…ne mode

jira case spark-6033 https://issues.apache.org/jira/browse/SPARK-6033

In standalone deploy mode, the cleanup will only remove the stopped application's directories.

The original description about the cleanup behavior is incorrect.

Author: 许鹏 <peng.xu@fraudmetrix.cn>

Closes #4803 from hseagle/spark-6033 and squashes the following commits:

927a6a0 [许鹏] fix the incorrect description about the spark.worker.cleanup in standalone mode
asfgit pushed a commit that referenced this pull request Feb 27, 2015
…ne mode

jira case spark-6033 https://issues.apache.org/jira/browse/SPARK-6033

In standalone deploy mode, the cleanup will only remove the stopped application's directories.

The original description about the cleanup behavior is incorrect.

Author: 许鹏 <peng.xu@fraudmetrix.cn>

Closes #4803 from hseagle/spark-6033 and squashes the following commits:

927a6a0 [许鹏] fix the incorrect description about the spark.worker.cleanup in standalone mode
@hseagle hseagle deleted the spark-6033 branch February 27, 2015 07:15
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