[jira] [Commented] (SPARK-3805) Enable Standalone worker cleanup by default
[
https://issues.apache.org/jira/browse/SPARK-3805?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14164485#comment-14164485
]
Aaron Davidson commented on SPARK-3805:
---
Upon further thought, I also agree with Patrick. My initial inclination was to
go back to the original behavior after the issue was resolved, but it seems
more dangerous to delete user data than to not delete it. A user who sees an
accumulation of state will look for a way to remove it (and find this feature),
but any user who needs to find now-deleted data is going to be irreversibly sad.
Enable Standalone worker cleanup by default
---
Key: SPARK-3805
URL: https://issues.apache.org/jira/browse/SPARK-3805
Project: Spark
Issue Type: Task
Components: Deploy
Reporter: Andrew Ash
Now that SPARK-1860 is fixed we should be able to turn on
{{spark.worker.cleanup.enabled}} by default
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org
[jira] [Commented] (SPARK-3805) Enable Standalone worker cleanup by default
[
https://issues.apache.org/jira/browse/SPARK-3805?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14164584#comment-14164584
]
Andrew Ash commented on SPARK-3805:
---
That sounds very reasonable -- I'll close. Maybe in the future we should have a
things to think about when going into production section of the docs but I
don't have the time to invest in that right now
Enable Standalone worker cleanup by default
---
Key: SPARK-3805
URL: https://issues.apache.org/jira/browse/SPARK-3805
Project: Spark
Issue Type: Task
Components: Deploy
Reporter: Andrew Ash
Now that SPARK-1860 is fixed we should be able to turn on
{{spark.worker.cleanup.enabled}} by default
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org
[jira] [Commented] (SPARK-3805) Enable Standalone worker cleanup by default
[
https://issues.apache.org/jira/browse/SPARK-3805?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14159711#comment-14159711
]
Apache Spark commented on SPARK-3805:
-
User 'ash211' has created a pull request for this issue:
https://github.com/apache/spark/pull/2664
Enable Standalone worker cleanup by default
---
Key: SPARK-3805
URL: https://issues.apache.org/jira/browse/SPARK-3805
Project: Spark
Issue Type: Task
Reporter: Andrew Ash
Now that SPARK-1860 is fixed we should be able to turn on
{{spark.worker.cleanup.enabled}} by default
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org
[jira] [Commented] (SPARK-3805) Enable Standalone worker cleanup by default
[
https://issues.apache.org/jira/browse/SPARK-3805?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14159837#comment-14159837
]
Patrick Wendell commented on SPARK-3805:
I commented on the PR - but because this deletes user data, I don't think it's
a good idea to enable it by default.
Enable Standalone worker cleanup by default
---
Key: SPARK-3805
URL: https://issues.apache.org/jira/browse/SPARK-3805
Project: Spark
Issue Type: Task
Reporter: Andrew Ash
Now that SPARK-1860 is fixed we should be able to turn on
{{spark.worker.cleanup.enabled}} by default
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org
