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

   ### What problem does this PR solve?
   
   Backport these three PRs together to `branch-4.2`:
   
   - https://github.com/apache/doris/pull/68628
   - https://github.com/apache/doris/pull/68328
   - https://github.com/apache/doris/pull/67759
   
   Early EOS requests can occupy all heavy workers while waiting for remaining 
senders, and cancellation can queue behind those same workers or block on 
channel/writer locks. Use an asynchronous sender-arrival barrier, isolate 
cancellation RPCs in a dedicated pool, and publish a shared cancellation status 
observed at flush and delete-bitmap work boundaries. Final-owner cleanup drains 
running callbacks before releasing writer resources.
   
   Keep branch-4.2's single-replica writes and row-index writer interfaces. 
Retain applicable local/cloud ordinary-writer, EOS, manager, service-routing, 
bitmap-token, and memory-reclamation unit coverage. Upstream group-rowset-only 
cases and the integration fixture requiring newer test/storage helpers are not 
included in this release backport.
   
   ### Release note
   
   Improve load cancellation responsiveness and prevent heavy-worker starvation 
during incremental-channel EOS close.
   
   ### Check List (For Author)
   
   - Test: Compilation and test execution intentionally skipped as requested. 
Passed `git diff --check`, changed-line/new-file clang-format 16.0.5 formatting 
checks, and local include-path verification. This release branch does not 
contain `build-support/check-build-hygiene.sh`; compilation-dependent analysis 
was not run.
   - Behavior changed: Yes; cancellation dispatch is isolated, cancellation 
publication avoids writer locks, and waiting EOS RPCs release heavy workers.
   - 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]

Reply via email to