zhijiangW opened a new pull request #11687: 
[FLINK-16536][network][checkpointing] Implement InputChannel state recovery for 
unaligned checkpoint
URL: https://github.com/apache/flink/pull/11687
 
 
   ## What is the purpose of the change
   
   During recovery process for unaligned checkpoint, the remote input channel 
state should also be recovered besides with existing operator states.
       
   The remote channel would request buffer and then interact with 
ChannelStateReader to fill in the state data.  The filled buffer would be 
inserted into respective data queue for processing in normal way.
   
   It should guarantee that the new data from upstream partition should not 
overtake the input state data to avoid mis-order issue.
   
   ## Brief change log
   
     - *Delay request partition in `RemoteInputChannel` after finishing reading 
channel state.*
     - *Add related interfaces method from input channel to handler stacks to 
notify the read of channel state*
     - *Implement the main process to read channel state via interacting with 
`ChannelStateReader`*
   
   ## Verifying this change
   
   Add some new unit tests to verify the changes
   
   ## 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:
us...@infra.apache.org


With regards,
Apache Git Services

Reply via email to