wsry opened a new pull request #12034:
URL: https://github.com/apache/flink/pull/12034


   ## What is the purpose of the change
   For unaligned checkpoint, task may consume data after the checkpoint barrier 
before performing checkpoint which lead to consumption of duplicated data and 
corruption of data stream.
   
   More specifically, when the Netty thread notifies the checkpoint barrier for 
the first time and enqueue a checkpointing task in the mailbox, the task thread 
may still in data consumption loop and if it reads a new checkpoint barrier 
from another channel it will not return to the mailbox and instead it will 
continue to read data until a all data consumed or we have a full record, 
meanwhile, the data after checkpoint barrier may be read and consumed which 
lead to inconsistency.
   
   This PR tries to fix the problem.
   
   ## Brief change log
   
     - Return to mailbox after receiving a checkpoint barrier.
   
   
   ## Verifying this change
   
   This change is already covered by existing 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/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