[
https://issues.apache.org/jira/browse/SPARK-20624?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17140124#comment-17140124
]
Holden Karau commented on SPARK-20624:
--------------------------------------
[~hyukjin.kwon] that doesn't seem comparable, the history service is an
existing feature with a lot of use and that involved 18 distinct
sub-components. If folks wanted an SPIP for it there was plenty of time from
when I shared the updated design doc, PR, and e-mailed the dev@ list.
> Add better handling for node shutdown
> -------------------------------------
>
> Key: SPARK-20624
> URL: https://issues.apache.org/jira/browse/SPARK-20624
> Project: Spark
> Issue Type: Improvement
> Components: Spark Core
> Affects Versions: 3.0.0
> Reporter: Holden Karau
> Priority: Major
>
> While we've done some good work with better handling when Spark is choosing
> to decommission nodes (SPARK-7955), it might make sense in environments where
> we get preempted without our own choice (e.g. YARN over-commit, EC2 spot
> instances, GCE Preemptiable instances, etc.) to do something for the data on
> the node (or at least not schedule any new tasks).
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org
