Gabriel39 opened a new pull request, #69701:
URL: https://github.com/apache/doris/pull/69701
### What problem does this PR solve?
The external file-cache tests depend on host disk/inode usage and inherited
backend settings. Under resource-limit or advance-eviction mode, cache blocks
can disappear between reads: the query-limit test observes an empty queue, the
statistics test cannot establish stable hit/read counts, and the feature test
times out while waiting for default flags to become zero.
Establish a scoped baseline for these three non-concurrent suites. Disable
upper read caches and inherited per-query limits, temporarily suppress advance
eviction, and use 100% disk thresholds while retaining the failure for a
genuinely full filesystem. Poll both mode flags across cache paths before
measuring data. Restore every backend setting through the existing
temporary-config helper, including on assertion failure.
For the feature test, drive resource-limit entry with zero thresholds and
advance-eviction entry with a one-percent threshold. A populated cache
directory consumes an inode, whose used percentage rounds up to at least one.
Nest threshold updates so the background monitor never observes an invalid
enter/exit ordering during application or restoration. Keep the existing query
results and cache assertions.
### Release note
None. Regression-test stability only.
### Check List (For Author)
- Test:
- [x] Reproduced all three original suite failures on a local
Doris/Hive/HDFS environment with two cache paths and resource-pressure settings.
- [x] All three complete suites passed with the standard five-second
background monitor, using the existing golden output.
- [x] All three suites passed three consecutive runs with a 100 ms
background monitor.
- [x] Verified backend configuration restoration after both successful
execution and an injected assertion failure.
- [x] No golden output changes; no FE/BE implementation changes.
- Behavior changed: No product behavior changes.
- Does this need documentation: No.
--
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]
