Support checkpoint GC in leader for mode stateful operators - #1112
Merged
Conversation
QnJ1c2kNCg
approved these changes
Jul 27, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR follows on the initial support for checkpoint GC in leader mode for stateless operators (#1076) by adding support for stateful operators as well. Stateful operators are much more complex to GC, because their state may be stored over many checkpoints. GC thus requires reachability analysis: we must determine that a state file is no longer reachable from any active checkpoint root before it may be deleted.
We do lose some of the nicer memory bounding properties of the previous implementation, which took a streaming approach to cleaning checkpoints, but that is largely unavoidable.