Skip to content

branch-4.1: [fix](streaming-job) Optimize snapshot offset persistence #66238 - #66539

Open
github-actions[bot] wants to merge 1 commit into
branch-4.1from
auto-pick-66238-branch-4.1
Open

branch-4.1: [fix](streaming-job) Optimize snapshot offset persistence #66238#66539
github-actions[bot] wants to merge 1 commit into
branch-4.1from
auto-pick-66238-branch-4.1

Conversation

@github-actions

@github-actions github-actions Bot commented Aug 6, 2026

Copy link
Copy Markdown
Contributor

Cherry-picked from #66238

### What problem does this PR solve?

Problem Summary:

Snapshot tasks persisted the complete offset provider after every split
commit, producing frequent edit logs while the snapshot state kept
growing. The previous default snapshot split size also produced too many
small snapshot tasks. Natural terminal transitions needed explicit
persistence so finished jobs replay with their terminal metadata.

This change:
- Limits snapshot offset edit logs with a mutable 300-second interval
while keeping binlog offset commits immediate.
- Increases the default snapshot split size from 8,096 to 40,960 rows,
while preserving explicitly configured values.
- Removes obsolete snapshot recovery state after the first committed
binlog offset for FROM-TO and CDC stream TVF jobs.
- Persists natural FINISHED transitions and restores terminal replay
fields and callbacks consistently.
- Adds focused unit coverage and a MySQL snapshot-only FE restart
regression case.
@github-actions
github-actions Bot requested a review from yiguolei as a code owner August 6, 2026 07:54
@hello-stephen

Copy link
Copy Markdown
Contributor

Thank you for your contribution to Apache Doris.
Don't know what should be done next? See How to process your PR.

Please clearly describe your PR:

  1. What problem was fixed (it's best to include specific error reporting information). How it was fixed.
  2. Which behaviors were modified. What was the previous behavior, what is it now, why was it modified, and what possible impacts might there be.
  3. What features were added. Why was this function added?
  4. Which code was refactored and why was this part of the code refactored?
  5. Which functions were optimized and what is the difference before and after the optimization?

@hello-stephen

Copy link
Copy Markdown
Contributor

run buildall

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants