[FEATURE] Broadcast the shuffle handle info for the reader
- Dominant language
- Java
- Stars
- 454
- Forks
- 172
- Avg merge
- 5d 17h
- Merged PRs (30d)
- 5
Description
### Code of Conduct
- [x] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct)
### Search before asking
- [x] I have searched in the [issues](https://github.com/apache/incubator-uniffle/issues?q=is%3Aissue) and found no similar issues.
### Describe the feature
In #2637 , we introduce the cache mechanism for the shuffle handle retrieving performance. Another optional proposal is to broadcast the shuffle handle info, that may be much better to reuse the spark network stack.
### Motivation
_No response_
### Describe the solution
_No response_
### Additional context
_No response_
### Are you willing to submit PR?
- [x] Yes I am willing to submit a PR!
Contributor guide
Research direction
Start by reading issue #2637 and the existing shuffle-handle retrieval and cache design it introduces. The issue does not identify files, tests, or a concrete solution; done would require an agreed design for broadcasting shuffle-handle information through the Spark network stack, followed by implementation and validation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, spark
- Domain
- distributed-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100