Myasuka opened a new pull request #7813: [FLINK-10712] Support to restore state when using RestartPipelinedRegionStrategy URL: https://github.com/apache/flink/pull/7813 ## What is the purpose of the change After [FLINK-11618](https://issues.apache.org/jira/browse/FLINK-11618) merged, previous [PR-7009](https://github.com/apache/flink/pull/7009) seems a bit outdated, just create this new PR based on previous discussion to replace the older one. Currently, `RestartPipelinedRegionStrategy` does not perform any state restore. This is big problem because all restored regions will be restarted with empty state. This PR supports to restore state when using `RestartPipelinedRegionStrategy`. ## Brief change log - Reload checkpointed state when `FailoverRegion` called `restart` method. ## Verifying this change This change added tests and can be verified as follows: - Added unit tests for `FailoverRegion` to ensure the failover region ever called new `restoreLatestCheckpointedState` API within `CheckpointCoordinator`. - Added new integration test `RegionFailoverITCase` to verify split redistribution and union state could be restored properly when the job consists multi regions. - Refactored `StreamFaultToleranceTestBase` to let all sub-classes ITs could failover with state using RestartPipelinedRegionStrategy. ## 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, Yarn/Mesos, ZooKeeper: **yes**, restore state when failover using RestartPipelinedRegionStrategy. - The S3 file system connector: **no** ## Documentation - Does this pull request introduce a new feature? **yes** - If yes, how is the feature documented? **JavaDocs**
---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected] With regards, Apache Git Services
