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

   ### What problem does this PR solve?
   
   Issue Number: close https://github.com/apache/doris/issues/61956
   
   Related PR: https://github.com/apache/doris/pull/63110
   
   Problem Summary:
   
   Currently, LSNs are assigned on the BE TabletWriter side during writes, with 
each node allocating them independently. 
   As a result, replicas may end up with inconsistent LSNs when reading.
   
   We are now moving LSN allocation to the sink side so that the same batch of 
data gets a fixed LSN. 
   At the same time, for publish-conflict cases, we preserve consistency by 
proactively reading the old LSN instead of allocating a new one.
   
   In addition,fix 2 bug about binlog:
   1. binlog compaction hasn't get cumulative policy, it will cause DCHECK fail
   2. read binlog may receive error, because preaggregation is false.
   
   ### Release note
   
   None
   
   ### Check List (For Author)
   
   - Test <!-- At least one of them must be included. -->
       - [ ] Regression test
       - [x] Unit Test
       - [x] 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.
       - [x] 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