dawidwys opened a new pull request #15146:
URL: https://github.com/apache/flink/pull/15146


   ## What is the purpose of the change
   
   This PR introduces an active, timer based time out for checkpoints 
alignment. After the time out we switch over to unaligned checkpoint. Compared 
to the passive time out it accounts for the situation that the barriers are 
stuck in the network stack for a considerable amount of time.
   
   
   ## Brief change log
   
   * Added `Clock` to the `AlternatingController` to ease up testing
   * Reworked static helper test methods into builders for 
CheckpointedInputGate and SingleInputBarrierHandler
   * Added methods for registering callbacks on time out via `TimerService` 
which are executed in the mailbox thread.
   
   
   ## Verifying this change
   
   Added tests in:
   * AlternatingControllerTest
   * Added one more test case in UnalignedCheckpointsITCase
   
   ## 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/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]


Reply via email to