XComp opened a new pull request, #24309:
URL: https://github.com/apache/flink/pull/24309

   ## What is the purpose of the change
   
   Quoting @zentol from 
[FLINK-34427](https://issues.apache.org/jira/browse/FLINK-34427?focusedCommentId=17816969&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-17816969)
 here:
   > The problem is the use of scheduled executors in the 
FineGrainedSlotManager. It periodically tries to schedule actions 
unconditionally into the main thread, and this periodic action is also never 
cancelled.
   > If the rpc endpoint shuts down during the periodic delay the scheduled 
action can fire again before the rpc service (and thus scheduled executor) is 
shut down, running into this error.
   
   > This code is plain broken as tt makes assumptions about the lifecycle of 
the scheduled executor. The loop should be canceled when the FGSM is shut down, 
and as a safety rail any scheduled action should validate that the FGSM is not 
shut down yet before scheduling anything into the main thread.
   
   ## Brief change log
   
   * Makes `ManuallyTriggeredScheduledExecutorService` more robust against 
exceptions
   * Adds state check to scheduled task
   
   ## Verifying this change
   
   * `FineGrainedSlotManagerTest#testCloseWithScheduledTask` was added
   
   ## 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, ZooKeeper: yes
     - The S3 file system connector: no
   
   ## Documentation
   
     - Does this pull request introduce a new feature? no
     - If yes, how is the feature documented? not applicable


-- 
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.

To unsubscribe, e-mail: issues-unsubscr...@flink.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

Reply via email to