freemandealer opened a new pull request, #63602:
URL: https://github.com/apache/doris/pull/63602
Problem Summary: The old sync file cache clear path bypassed the normal
FileBlock lifecycle and was not safe with concurrent cache users, while the
async clear path only marked or enqueued deletes and returned before held
blocks, recycle-queue deletes, and file-cache meta deletes were finished. This
change makes the factory sync clear path use a synchronous wrapper over the
async clear semantics. The wrapper serializes clear operations, pauses the TTL
manager during clear, marks existing blocks for deletion, drains recycled
blocks, waits for held deleting blocks to be released, and waits for file-cache
meta delete fences before reporting completion. The direct clear helper is kept
only for BE tests. HTTP sync clear now runs through a cancellable async reply
path so client disconnects can cancel waiting without adding a clear timeout
config.
### 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]
