-
Notifications
You must be signed in to change notification settings - Fork 13.5k
[FLINK-37008] [runtime-web] Flink UI should show the type of checkpoint (full vs incremental) #25899
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Closed
ryanvanhuuksloot
wants to merge
9
commits into
apache:master
from
ryanvanhuuksloot:rvh.ui-full-checkpoints
Closed
[FLINK-37008] [runtime-web] Flink UI should show the type of checkpoint (full vs incremental) #25899
Changes from all commits
Commits
Show all changes
9 commits
Select commit
Hold shift + click to select a range
028bfba
First attempt at Full Checkpoint information on the UI
ryanvanhuuksloot 1494ec2
Add an example UI Change
ryanvanhuuksloot c362d7a
[FLINK-37008] Swap to 'incremental'
ryanvanhuuksloot ca8b457
[FLINK-37008] Address comments
ryanvanhuuksloot e132d2b
[FLINK-37008] Swap strategy logic
ryanvanhuuksloot 5e87656
[FLINK-37008] PR Comments
ryanvanhuuksloot 6d03515
[FLINK-37008] Remove analytics
ryanvanhuuksloot 4ba9503
[FLINK-37008] Fix CI
ryanvanhuuksloot 917fe0f
Not sure what is in here
ryanvanhuuksloot File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why those are introduced?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
They are only used for tests
We don't really have an test suite for testing this kind of thing
I'm open to ideas for where to add tests
I've thought about
SnapshotUtilsTest
and
CheckpointPropertiesTest
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ah, I see.
I read through the
CheckpointCoordinator
and it seems the JM will always propagate incremental checkpoints periodically (not the ones triggered by Rest API). But actually the TM will do incremental or full ones by configuration it reads (createRocksNativeFullSnapshotStrategy
orRocksIncrementalSnapshotStrategy
when state backend build). Meaning that in UI will always show incremental cps even if we disable that. Am I right? If so, we should make some change inCheckpointCoordinator
.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I agree looking at the
CheckpointCoordinator
.flink/flink-runtime/src/main/java/org/apache/flink/runtime/checkpoint/CheckpointCoordinator.java
Lines 355 to 356 in 55de8d6
Specifically, the issue is that
Checkpoint
can be used for both full or incremental.flink/flink-runtime/src/main/java/org/apache/flink/runtime/checkpoint/CheckpointType.java
Lines 29 to 31 in 55de8d6
We'd have to move the evaluation of
execution.checkpointing.incremental
or change how we are determining if a Checkpoint is Full 🤔There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I thought a possible solution is to evaluate
execution.checkpointing.incremental
inCheckpointCoordinator
and setcheckpointProperties
properly. WDTY?