mridulm opened a new pull request, #2639:
URL: https://github.com/apache/celeborn/pull/2639
<!--
Thanks for sending a pull request! Here are some tips for you:
- Make sure the PR title start w/ a JIRA ticket, e.g. '[CELEBORN-XXXX]
Your PR title ...'.
- Be sure to keep the PR description updated to reflect all changes.
- Please write your PR title to summarize what this PR proposes.
- If possible, provide a concise example to reproduce the issue for a
faster review.
-->
### What changes were proposed in this pull request?
Adds support for barrier stages.
This involves two aspects:
a) If there is a task failure when executing a barrier stage, all shuffle
output for the stage attempt are discarded and ignored.
b) If there is a reexecution of a barrier stage (for ex, due to child stage
getting a fetch failure), all shuffle output for the previous stage attempt are
discarded and ignored.
This is similar to handling of indeterminate stages when
`throwsFetchFailure` is `true`.
Note that this is supported only when
`spark.celeborn.client.spark.fetch.throwsFetchFailure` is `true`
### Why are the changes needed?
As detailed in CELEBORN-1518, Celeborn currently does not support barrier
stages; which is an essential functionality in Apache Spark which is widely in
use by Spark users.
Enhancing Celeborn will allow its use for a wider set of Spark users.
### Does this PR introduce _any_ user-facing change?
Adds ability for Celeborn to support Apache Spark Barrier stages.
### How was this patch tested?
Existing tests, and additional tests (thanks to @jiang13021 in #2638)
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
