Details
-
Improvement
-
Status: Closed
-
Major
-
Resolution: Fixed
-
None
Description
The current ShuffleMaster has an unclear lifecycle which is inconsistent with the ShuffleEnvironment at the TM side. Besides, it is hard to Implement some important capabilities for remote shuffle service. For example, 1) release external resources when a job finished; 2) Stop or start tracking some partitions depending on the status of the external service or system.
We drafted a document[1] which proposed some simple changes to solve these issues. The document is still not wholly completed yet. We will start a discussion once it is finished.
[1] https://docs.google.com/document/d/1_cHoapNbx_fJ7ZNraSqw4ZK1hMRiWWJDITuSZrdMDDs/edit?usp=sharing
Attachments
Issue Links
- is related to
-
FLINK-22672 Some enhancements for pluggable shuffle service framework
- Closed
- links to