branch-4.1: [improvement](streamingjob) change streaming job source log lag in bytes #66409 - #67187
Merged
Merged
Conversation
…tes (#66409) ### What problem does this PR solve? Issue Number: N/A Related PR: #62269 Problem Summary: Streaming job lag was calculated from the current time and the timestamp of the last consumed event. The value kept increasing when the source was idle, so it could not distinguish source inactivity from an actual synchronization backlog. This change reports source-log backlog in bytes. MySQL-compatible sources calculate the remaining bytes from the committed binlog file and position to the current end offset. PostgreSQL calculates the WAL byte difference from the replication slot confirmed position to the current WAL position. Snapshot-only jobs report `-1`, and transient lag calculation failures retain the latest successful observation. The `jobs("type"="insert")` output renames `Lag` to `LagBytes` and adds `LastSourceEventTimestamp`. The new field is the Unix timestamp in seconds of the latest source binlog or WAL event recorded in the job's committed offset. MySQL-compatible sources use `ts_sec`, while PostgreSQL converts `ts_usec` to seconds. It is empty before a source event timestamp is available. The existing formatted `LastTaskSuccessTime` remains unchanged. The per-job Prometheus metrics now expose: - `doris_fe_streaming_job_per_job_lag_bytes` - `doris_fe_streaming_job_per_job_last_source_event_timestamp_seconds` - `doris_fe_streaming_job_per_job_last_task_success_time_seconds` The two timestamp metrics are Unix seconds. A value of `0` means that the corresponding source event or successful task has not been observed yet.
Contributor
|
Thank you for your contribution to Apache Doris. Please clearly describe your PR:
|
Contributor
|
run buildall |
Contributor
FE UT Coverage ReportIncrement line coverage |
yiguolei
approved these changes
Aug 27, 2026
Contributor
Author
|
PR approved by anyone and no changes requested. |
github-actions
Bot
added
the
approved
Contributor
Author
|
PR approved by at least one committer and no changes requested. |
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
3 participants
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.
Cherry-picked from #66409