[
https://issues.apache.org/jira/browse/SPARK-20178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15957341#comment-15957341
]
Sital Kedia commented on SPARK-20178:
-------------------------------------
[~tgraves] Thanks for creating the JIRA and driving the discussion
[~tgraves], [~imranr], [~markhamstra], [~kayousterhout] - . As discussed over
the PR, I have created a doc consolidating the issues related to fetch failure
and a high-level design goals for the scheduler
https://docs.google.com/document/d/1D3b_ishMfm5sXmRS494JrOJmL9V_TRVZUB4TgK1l1fY/edit?usp=sharing.
Please take a look and let me know what you think. Once we reach a consensus
about the desired behavior and identify the changes that needs to be done, I
can work on having more detailed design doc and also split the change into
multiple small logical PRs.
> Improve Scheduler fetch failures
> --------------------------------
>
> Key: SPARK-20178
> URL: https://issues.apache.org/jira/browse/SPARK-20178
> Project: Spark
> Issue Type: Epic
> Components: Scheduler
> Affects Versions: 2.1.0
> Reporter: Thomas Graves
>
> 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
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
