igalshilman opened a new pull request #9171: [FLINK-13326] Support asynchronous writing to raw operator (and raw keyed) state URL: https://github.com/apache/flink/pull/9171 ## What is the purpose of the change Currently, the users of the `AbstractStreamOperator` class, are expected to complete the writing of `rawKeyedOperatorState` and `rawOperatorState` in the synchronous part of a snapshot (before the completion of `snapshotState` method) But sometimes it is desirable to snapshot a custom data structure asynchronously (i.e. out side of the snapshotState method) in a similar way that the other state backends allow. This PR adds the ability to suspend the closing of the raw states streams in `snapshotState` outside of the snapshotState method, and hence effectively support async snapshots for raw states. Flink snapshotting logic already supports splitting the snapshot to sync and async parts for the various state backends, therefore the changes introduced in this PR mainly reuse that logic. ## Brief change log - Add an interruptible close method to `ResourceGuard` (the default is still unInterruptible). - Add and use a ResourceGuard in `NonClosingCheckpointOutputStream`. - modify the `StateSnapshotContextSynchronousImpl#getRaw*OperatorStateOutput` to return a future that completes after all the leases were released. ## 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, 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] With regards, Apache Git Services
