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

   ### What problem does this PR solve?
   
     ## Problem
   
     Two race conditions exist in dictionary version lifecycle between FE and 
BE:
   
     **1. FE version ahead of BE commit (N+1 vs N)**
     FE `dataLoad()` calls `increaseVersion()` before sending 
`commitNowVersion()` RPC to BE . 
   During this window, queries with `dict_get(version_id=N+1)` fail on BE with 
"dictionary not found".
   
     **2. BE GCs old version while in-flight query still uses it (N+1 vs N)**
     BE previously stored only one version per dict. After a new version N+1 is
     committed, the old version N is immediately overwritten. In-flight queries
     that started with version N (already planned on FE) then fail on BE because
     version N no longer exists.
   
   
   ### Release note
   
   None
   
   ### Check List (For Author)
   
   - Test <!-- At least one of them must be included. -->
       - [x] Regression test
       - [x] 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