Skip to content

branch-4.1: [fix](delta writer) Fix shared delta writer state lifetime #64349#64468

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

branch-4.1: [fix](delta writer) Fix shared delta writer state lifetime #64349#64468
github-actions[bot] wants to merge 1 commit into
branch-4.1from
auto-pick-64349-branch-4.1

Conversation

@github-actions

Copy link
Copy Markdown
Contributor

Cherry-picked from #64349

### What problem does this PR solve?

Issue Number: None

Problem Summary:

Shared `DeltaWriterV2` instances can be reused by multiple local sinks
from the same load. Before this change, the shared writer stored the
`RuntimeState*` from the sink that first created it. If that creator
sink finished and its `RuntimeState` was destroyed while another local
sink continued to reuse the shared writer, `DeltaWriterV2::write()`
could access the destroyed state in the memtable flush-limit
cancellation path, causing a BE crash or ASAN use-after-free.

This PR adds a BE unit test that reproduces the lifetime boundary:

- one `VTabletWriterV2` creates the shared `DeltaWriterV2`;
- the creator writer and its `RuntimeState` are destroyed without
cancelling the shared writer;
- a second writer reuses the shared writer and is forced into the
`DeltaWriterV2::write()` flush-limit wait path;
- the old code reads the destroyed creator state, while the fixed code
observes the current writer's cancel state and exits cleanly.

The fix removes the stored `RuntimeState*` from `DeltaWriterV2`. The
shared writer now keeps only the stable `WorkloadGroup` shared pointer
needed by `MemTableWriter` initialization, and `VTabletWriterV2` passes
a per-call cancel checker into `DeltaWriterV2::write()` so cancellation
is evaluated against the current sink.

### Release note

Fix a possible BE crash when shared delta writers are reused by multiple
local sinks.
@github-actions github-actions Bot requested a review from yiguolei as a code owner June 12, 2026 13:43
@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