You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Venkat Sambath (Jira)" <ji...@apache.org> on 2022/01/15 23:40:00 UTC
[jira] [Commented] (SPARK-20178) Improve Scheduler fetch failures
[ https://issues.apache.org/jira/browse/SPARK-20178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17476710#comment-17476710 ]
Venkat Sambath commented on SPARK-20178:
----------------------------------------
Is design doc referenced in this jira https://docs.google.com/document/d/1D3b_ishMfm5sXmRS494JrOJmL9V_TRVZUB4TgK1l1fY/edit?usp=sharing available anywhere else?
> Improve Scheduler fetch failures
> --------------------------------
>
> Key: SPARK-20178
> URL: https://issues.apache.org/jira/browse/SPARK-20178
> Project: Spark
> Issue Type: Epic
> Components: Scheduler, Spark Core
> Affects Versions: 2.1.0
> Reporter: Thomas Graves
> Priority: Major
> Labels: bulk-closed
>
> We have been having a lot of discussions around improving the handling of fetch failures. There are 4 jira currently related to this.
> We should try to get a list of things we want to improve and come up with one cohesive design.
> SPARK-20163, SPARK-20091, SPARK-14649 , and SPARK-19753
> I will put my initial thoughts in a follow on comment.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org