reswqa opened a new pull request, #21122:
URL: https://github.com/apache/flink/pull/21122
## What is the purpose of the change
*Hybrid shuffle does not support multiple consumer for single subpartition
data. This will bring some defects, such as the inability to support partition
reuse, speculative execution. In particular, it cannot support broadcast
optimization, that is, hybrid shuffle writes multiple copies of broadcast data,
This will cause a waste of memory and disk space and affect the performance of
shuffle write phase. Ideally, for the full spilling strategy, any broadcast
data (record or event) should only write one piece of data in the memory, and
the same is true for the disk.*
## Brief change log
- *full spilling strategy is no long consider consumer offset*
- *supports multiple consumer.*
- *supports broadcast optimize*
## Verifying this change
This change added unit tests.
## Does this pull request potentially affect one of the following parts:
- Dependencies (does it add or upgrade a dependency): no
- The public API, i.e., is any changed class annotated with
`@Public(Evolving)`: no
- The serializers: no
- The runtime per-record code paths (performance sensitive): no
- Anything that affects deployment or recovery: JobManager (and its
components), Checkpointing, Kubernetes/Yarn, ZooKeeper: no
- The S3 file system connector: no
## Documentation
- Does this pull request introduce a new feature? no
--
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]
