[ 
https://issues.apache.org/jira/browse/FLINK-22910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17394648#comment-17394648
 ] 

Yingjie Cao commented on FLINK-22910:
-------------------------------------

Resolved via 
81e1db3c439c1758dccd1a20f2f6b70120f48ef7...80df36b51af791f67126e07e182015ea6ea73fd2.

> Refine ShuffleMaster lifecycle management for pluggable shuffle service 
> framework
> ---------------------------------------------------------------------------------
>
>                 Key: FLINK-22910
>                 URL: https://issues.apache.org/jira/browse/FLINK-22910
>             Project: Flink
>          Issue Type: Improvement
>          Components: Runtime / Coordination
>            Reporter: Yingjie Cao
>            Assignee: Yingjie Cao
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 1.14.0
>
>
> 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



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to