zhuzhurk opened a new pull request #7255: [FLINK-10945] Use 
InputDependencyConstraint to avoid resource dead…
URL: https://github.com/apache/flink/pull/7255
 
 
   …locks in LAZY_FROM_SOURCES scheduling when resources are limited
   
   ## What is the purpose of the change
   
   This PR add a job config InputDependencyConstraint, which helps to avoid 
resource deadlocks in LAZY_FROM_SOURCES scheduling when resources are limited, 
as described in 
[FLINK-10945](https://issues.apache.org/jira/browse/FLINK-10945).
   
   ## Brief change log
   
    - *Add InputDependencyConstraint to ExecutionConfig*
    - *Adjust isConsumable interface in IntermediateResultPartition to fit for 
the data actual consumable definition*
    - Change current execution lazy scheduling logic(in 
Execution.scheduleOrUpdateConsumers(edges)) to schedule tasks only if the 
InputDependencyConstraint is satisfied(an interface 
ExecutionVertex.checkInputDependencyConstraints is added to serve this 
purpose). 
   
   
   ## Verifying this change
   
   This change added tests and can be verified as follows:
   
     - *Added IntermediateResultPartitionTest to validate 
IntermediateResultPartition changes*
     - *Added ExecutionVertexInputConstraintTest to validate the constraint 
check logic in ExecutionVertex*
   
   ## 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)`: (yes)
     - The serializers: (no)
     - The runtime per-record code paths (performance sensitive): (no)
     - Anything that affects deployment or recovery: JobManager (and its 
components), Checkpointing, Yarn/Mesos, ZooKeeper: (yes)
     - The S3 file system connector: (no)
   
   ## Documentation
   
     - Does this pull request introduce a new feature? (yes)
     - If yes, how is the feature documented? (JavaDocs)
   

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

Reply via email to