Skip to content

branch-4.1: [fix](be) Preserve tablet ID in synchronous file cache writes #68310 - #68347

Merged
yiguolei merged 1 commit into
branch-4.1from
auto-pick-68310-branch-4.1
Sep 23, 2026
Merged

yiguolei merged 1 commit into
branch-4.1from
auto-pick-68310-branch-4.1

Conversation

@github-actions

Copy link
Copy Markdown
Contributor

Cherry-picked from #68310

The synchronous CachedRemoteFileReader path constructed CacheContext
without copying the reader tablet ID. Cache misses were downloaded
correctly, but newly created FileBlock and persisted block metadata used
the no-tablet sentinel 0. Runtime per-tablet cache inspection and TTL
registration therefore could not associate those new blocks with their
Doris tablet.

This change propagates the Doris tablet ID into the synchronous cache
context. External readers are normalized to the existing no-tablet
sentinel 0 for both synchronous and asynchronous writes, and TTL
registration defensively accepts only positive tablet IDs.

### Release note

Fix synchronous file cache blocks to retain their Doris tablet ID while
preserving no-tablet metadata for external readers.
@github-actions
github-actions Bot requested a review from yiguolei as a code owner September 21, 2026 16:49
@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

1 similar comment
@liaoxin01

Copy link
Copy Markdown
Contributor

run buildall

@hello-stephen

Copy link
Copy Markdown
Contributor

BE Regression && UT Coverage Report

Increment line coverage 100.00% (3/3) 🎉

Increment coverage report
Complete coverage report

Category Coverage
Function Coverage 74.58% (31514/42254)
Line Coverage 58.76% (351016/597339)
Region Coverage 55.47% (292798/527877)
Branch Coverage 56.33% (132122/234567)

@hello-stephen

Copy link
Copy Markdown
Contributor

BE Regression && UT Coverage Report

Increment line coverage 100.00% (3/3) 🎉

Increment coverage report
Complete coverage report

Category Coverage
Function Coverage 74.56% (31503/42254)
Line Coverage 58.73% (350841/597339)
Region Coverage 55.47% (292827/527877)
Branch Coverage 56.31% (132080/234567)

@github-actions

Copy link
Copy Markdown
Contributor Author

PR approved by anyone and no changes requested.

@github-actions github-actions Bot added the approved Indicates a PR has been approved by one committer. label Sep 23, 2026
@github-actions

Copy link
Copy Markdown
Contributor Author

PR approved by at least one committer and no changes requested.

@yiguolei
yiguolei merged commit 3669397 into branch-4.1 Sep 23, 2026
35 of 36 checks passed
yiguolei pushed a commit that referenced this pull request Sep 23, 2026
…ites #68310 (#68347)

Cherry-picked from #68310

Co-authored-by: Xin Liao <liaoxin@selectdb.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by one committer. reviewed

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants