[#2506] feat(spark3): Introduce option to enable reorder multi servers for reader #2507
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 option to enable reorder multi servers for reader
Why are the changes needed?
If partition splitting is enabled, large partitions will be distributed across multiple shuffle servers. With the help of Spark AQE (Adaptive Query Execution), these large partitions will be processed by multiple tasks.
In this case, all split tasks may sequentially read from the same set of shuffle servers, which can lead to high RPC concurrency pressure on specific servers.
This PR introduces the ability to randomly reorder the underlying shuffle servers to achieve better load balancing during reading.
Does this PR introduce any user-facing change?
Yes.
rss.client.read.reorderMultiServersEnable=false
How was this patch tested?
Needn't