[CELEBORN-1645] Introduce ShuffleFallbackPolicy to support custom implementation of shuffle fallback policy for CelebornShuffleFallbackPolicyRunner #2807
+349
−146
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What changes were proposed in this pull request?
Introduce
ShuffleFallbackPolicy
to support custom implementation of shuffle fallback policy forCelebornShuffleFallbackPolicyRunner
.Why are the changes needed?
Shuffle fallback policy is fixed in
CelebornShuffleFallbackPolicyRunner
, which could not support user-defined fallback policy implementation. It's proposed to introduceShuffleFallbackPolicy
to support custom implementation of shuffle fallback policy forCelebornShuffleFallbackPolicyRunner
.Does this PR introduce any user-facing change?
Introduce
ShuffleFallbackPolicy
interface to determine whether fallback to vanilla Spark built-in shuffle implementation.How was this patch tested?
SparkShuffleManagerSuite