freemandealer opened a new pull request, #63410:
URL: https://github.com/apache/doris/pull/63410
### What problem does this PR solve?
Issue Number: None
Related PR: None
Problem Summary: When file cache LRU restore creates a block from dump
metadata and later lazy loading finds the same hash/offset with a smaller real
file size, reset_range only updated the LRU queue size and _cur_cache_size. The
FileBlock range still kept the old restored size, so a later async clear or
eviction subtracted the old block size and could underflow _cur_cache_size,
producing huge size_percent values in need-evict-cache-in-advance logs. This
change makes reset_range update the FileBlock range as the single place that
keeps the FileBlock, LRU queue, _cur_cache_size, and TTL size accounting
consistent. FileBlock::finalize now delegates the range shrink to reset_range
instead of changing the range before calling it.
### Release note
None
### What problem does this PR solve?
Issue Number: close #xxx
Related PR: #xxx
Problem Summary:
### Release note
None
### Check List (For Author)
- Test <!-- At least one of them must be included. -->
- [ ] Regression test
- [ ] Unit Test
- [ ] Manual test (add detailed scripts or steps below)
- [ ] No need to test or manual test. Explain why:
- [ ] This is a refactor/code format and no logic has been changed.
- [ ] Previous test can cover this change.
- [ ] No code files have been changed.
- [ ] Other reason <!-- Add your reason? -->
- Behavior changed:
- [ ] No.
- [ ] Yes. <!-- Explain the behavior change -->
- Does this need documentation?
- [ ] No.
- [ ] Yes. <!-- Add document PR link here. eg:
https://github.com/apache/doris-website/pull/1214 -->
### Check List (For Reviewer who merge this PR)
- [ ] Confirm the release note
- [ ] Confirm test cases
- [ ] Confirm document
- [ ] Add branch pick label <!-- Add branch pick label that this PR should
merge into -->
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
