mxm opened a new pull request #11473: [FLINK-16705] Ensure MiniCluster shutdown 
does not interfere with JobResult retrieval
URL: https://github.com/apache/flink/pull/11473
 
 
   ## What is the purpose of the change
   
   There is a race condition in `LocalExecutor` between (a) shutting down the
   cluster when the job has finished and (b) the client which retrieves the 
result
   of the job execution.
   
   This was observed in Beam, running a large test suite with the Flink Runner.
   
   ## Brief change log
   
   We should make sure the job result retrieval and the cluster shutdown do not
   interfere. This adds a PerJobMiniClusterClient which guarantees that.
   
   
   ## Verifying this change
   
   This change added tests, see `PerJobMiniClusterClientTest` and 
`LocalExecutorITCase`.
   
   ## 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/Mesos, ZooKeeper: (no)
     - The S3 file system connector: (no)
   
   ## Documentation
   
     - Does this pull request introduce a new feature? (no)
     - 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 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