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

   ## What is the purpose of the change
   
   Currently many operators when processing watermarks, are firing multiple 
timers each producing potentially multiple output records. If this happens 
under back-pressure, it can quite easily block the subtask thread in the hard 
back-pressure state for an extended period of time blocking mailbox from 
processing any incoming mails, like processing checkpoint barriers and 
completing unaligned checkpoints.
   
   To address this issue, we would like to propose to make firing multiple 
timers interruptible in such a way, that Flink would be able to interrupt 
firing timers, perform checkpoint and return back to firing timers.
   
   ## Brief change log
   
   Please check individual commit messages.
   
   ## Verifying this change
   
   Covered by both existing tests and added new tests.
   
   ## 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, Kubernetes/Yarn, 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.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to