zhuzhurk opened a new pull request #10007: [FLINK-14060][runtime] Set slot 
sharing groups according to logical pipelined regions
URL: https://github.com/apache/flink/pull/10007
 
 
   ## What is the purpose of the change
   
   This PR is to set vertex slot sharing groups according to logical pipelined 
regions.
   It is a pre-requisite of FLINK-14062: Set managed memory fractions according 
to slot sharing groups.
   The changes are based on #9797 and #10006
   
   The slot sharing group of a vertex is determined as:
   - if a vertex slot sharing group is specified to be null, the slot sharing 
group is null
   - if a vertex slot sharing group is specified to be a non-default value(the 
group name not "default"), it will be respected
   - if a vertex slot sharing group is "default", it will be the slot sharing 
group of the vertex's logical pipelined region
   
   The slot sharing group of a region is determined as:
   - if allVerticesInSameSlotSharingGroupByDefault is true, all regions are in 
the same "default" slot sharing group
   - if allVerticesInSameSlotSharingGroupByDefault is false, all regions will 
be in distinct slot sharing groups
   
   ## Brief change log
   
     - *set vertex slot sharing group according to its logical pipelined 
regions.*
   
   ## Verifying this change
   
   This change added tests and can be verified as follows:
   
     - *Added tests to verify slot sharing group assigning*
   
   ## Does this pull request potentially affect one of the following parts:
   
     - Dependencies (does it add or upgrade a dependency): (yes / **no**)
     - The public API, i.e., is any changed class annotated with 
`@Public(Evolving)`: (yes / **no**)
     - The serializers: (yes / **no** / don't know)
     - The runtime per-record code paths (performance sensitive): (yes / **no** 
/ don't know)
     - Anything that affects deployment or recovery: JobManager (and its 
components), Checkpointing, Yarn/Mesos, ZooKeeper: (**yes** / no / don't know)
     - The S3 file system connector: (yes / **no** / don't know)
   
   ## Documentation
   
     - Does this pull request introduce a new feature? (yes / **no**)
     - If yes, how is the feature documented? (**not applicable** / docs / 
JavaDocs / not documented)
   

----------------------------------------------------------------
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.
 
For queries about this service, please contact Infrastructure at:
[email protected]


With regards,
Apache Git Services

Reply via email to