[SPARK-52506][CORE] Allow migrating to fallback storage only #51201
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
dongjoon-hyun
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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?
Allow to disable shuffle data migration to other executors thus only migrate shuffle data to fallback storage.
Why are the changes needed?
Currently, even though fallback storage is enabled, shuffle data are migrated to other executors first. This causes shuffle data to be migrated multiple times. Only when no other executor is available for migration, shuffle data are migrated to the fallback storage. There should be a mode of operation where executors migrate there shuffle data to the fallback storage only, so there the data is migrated exactly once.
Does this PR introduce any user-facing change?
No
How was this patch tested?
Unit test and manual test via reproduction example.
Was this patch authored or co-authored using generative AI tooling?
No