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

   ### What problem does this PR solve?
   
   
   Queries with a shared scan limit could hang when the limit was exhausted 
while `ScannerContext` still had pending scan tasks. `_pull_next_scan_task()` 
returned `nullptr` without scheduling those tasks, so the scanner lifecycle 
could stop making progress and the pipeline waited until query timeout.
   
   This change removes the shared-limit early return from 
`ScannerContext::_pull_next_scan_task()`. Pending scanners are submitted 
normally, and the exhausted shared limit is handled in `Scanner::get_block()`, 
which returns EOS before reading more data. 
`ScannerContext::get_block_from_queue()` then consumes the EOS tasks and marks 
the context finished after the in-flight scanners have completed.
   
   ### 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]

Reply via email to