rkhachatryan opened a new pull request #16510:
URL: https://github.com/apache/flink/pull/16510


   ## What is the purpose of the change
   
   For the changelog state backend, state ownership model
   is changed from pure-JM to a mixed one, in which JM only owns
   the shared state (resulting from rescaling or sharing files).
   
   This PR adds support for such shared state management (mostly JM side):
   - introduce StateObjectID (and refactor existing related classes) 
1456251ea104bfa31f895928a1809dcd5117a664
   - compute shared state on recovery (in `StateAssignmentOperation`) 
e4f43924338b2bc62d3c5b2f4d669401d903e0ad
   - inject those shared states into `TaskStateSnapshots` (TM) and 
`SharedStateRegistry` (JM)
   
   To achieve this it introduces a visitor pattern to traverse StateObject 
hierarchies (539928c9e096c9d991d069721e6853a2cd236311).
   
   cc: @StephanEwen, @tillrohrmann 
   
   ## Brief change log
   
   ## Verifying this change
   - `SharedStateCollectorTest`
   - `StateObjectIdCollectingVisitorTest`
   - TBD: tests for `StateObject.accept()` implementations
   
   This change is a trivial rework without any test coverage.
   
   ## 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/Mesos, 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? no
   


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