sollhui opened a new pull request, #69979:
URL: https://github.com/apache/doris/pull/69979

   ### What problem does this PR solve?
   
   During adaptive random bucket loading, 
`VNodeChannel::_set_adaptive_random_bucket_open_request()` normally skips 
selected tablets that do not belong to the current node channel. Logging a 
WARNING for every skipped tablet can flood both INFO and WARNING logs when many 
partitions and parallel writers are involved, increasing disk I/O and evicting 
useful diagnostic history.
   
   Change this expected filtering message to `VLOG_DEBUG`, which is disabled by 
default. Keep the existing diagnostic fields, tablet selection logic, and 
warnings for unknown partitions, unknown indexes, and invalid bucket sequences 
unchanged.
   
   ### Release note
   
   Avoid excessive BE INFO/WARNING logging when adaptive random bucket loading 
skips non-local tablets.
   
   ### Check List (For Author)
   
   - Test
       - [ ] Regression test
       - [ ] Unit Test
       - [ ] Manual test (add detailed scripts or steps below)
       - [x] No need to test or manual test. Explain why:
           - [x] Other reason: logging-level-only change; no data-path logic 
changes. Ran `build-support/clang-format.sh` and 
`build-support/check-format.sh` with clang-format 16, and `git diff --check`. 
Source review verified that the only semantic change is `LOG(WARNING)` to 
`VLOG_DEBUG`, whose default verbosity is disabled. Full BE compilation and 
runtime regression tests were not run because local third-party build 
dependencies are unavailable.
   
   - Behavior changed:
       - [ ] No.
       - [x] Yes. Expected non-local tablet filtering is logged only when debug 
verbosity is enabled.
   
   - Does this need documentation?
       - [x] No.
       - [ ] Yes.
   
   ### Check List (For Reviewer who merge this PR)
   
   - [ ] Confirm the release note
   - [ ] Confirm test cases
   - [ ] Confirm document
   - [ ] Add branch pick label
   


-- 
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]

Reply via email to