[flink] support offset lag#3350
Open
zuston wants to merge 1 commit into
Open
Conversation
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
1 participant
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.
Purpose
Linked issue: close #3349
Flink currently exposes
currentFetchEventTimeLag, but it measures event-time lag rather than offset backlog. For Fluss log reading, we need a Kafka-style records lag metric so users can understand how far each subscribed source-reader bucket is behind.Relying only on timestamp lag can be misleading, especially for backfill jobs that subscribe to multiple time partitions. Older partitions may always appear to have a large event-time lag, even when their records have already been fully consumed.
Brief change log
Tests
API and Format
Documentation