Skip to content

branch-4.2: [fix](fe) Avoid Meta Service queries during streaming job replay #69498 - #69537

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

github-actions[bot] wants to merge 1 commit into
branch-4.2from
auto-pick-69498-branch-4.2

Conversation

@github-actions

Copy link
Copy Markdown
Contributor

Cherry-picked from #69498

)

### What problem does this PR solve?

Issue Number: N/A

Related PR: #57264

Problem Summary:

Cloud streaming jobs query Meta Service for progress while replaying
each job update journal, making FE replay depend on Meta Service
availability and RPC latency. ALTER already persists the updated offset
provider state and job statistics in the journal.

Restore the provider state and cloud statistics locally during replay
instead of querying Meta Service. A paused job therefore retains its
altered offset and journaled statistics after an FE restart, before
RESUME. PENDING scheduling still fetches the authoritative committed
progress from Meta Service before dispatching tasks, and pauses the job
if that fetch fails.

### Release note

Cloud streaming jobs restore journaled offsets and statistics during FE
replay without querying Meta Service. Progress is still synchronized
from Meta Service before consumption resumes.
@github-actions
github-actions Bot requested a review from yiguolei as a code owner October 23, 2026 11:16
@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