-
Notifications
You must be signed in to change notification settings - Fork 3.7k
[fix](cloud) potential data race when retrying prepare/commit rowset for load #51129
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
Thank you for your contribution to Apache Doris. Please clearly describe your PR:
|
|
run buildall |
|
run buildall |
12c02b7 to
ffb0128
Compare
|
run buildall |
TPC-H: Total hot run time: 33716 ms |
TPC-DS: Total hot run time: 192328 ms |
ClickBench: Total hot run time: 29.58 s |
ffb0128 to
08c3697
Compare
|
run buildall |
TPC-H: Total hot run time: 33958 ms |
TPC-DS: Total hot run time: 193674 ms |
ClickBench: Total hot run time: 29.95 s |
BE UT Coverage ReportIncrement line coverage Increment coverage report
|
BE Regression && UT Coverage ReportIncrement line coverage Increment coverage report
|
|
run buildall |
1 similar comment
|
run buildall |
Cloud UT Coverage ReportIncrement line coverage Increment coverage report
|
TPC-H: Total hot run time: 33880 ms |
TPC-DS: Total hot run time: 192763 ms |
ClickBench: Total hot run time: 29.73 s |
BE UT Coverage ReportIncrement line coverage Increment coverage report
|
BE Regression && UT Coverage ReportIncrement line coverage Increment coverage report
|
|
PR approved by at least one committer and no changes requested. |
|
PR approved by anyone and no changes requested. |
dataroaring
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
…for load (#51129) If the transaction has been finished, it means the prepare/commit rowset is a timeout retry request. In this case, do not write the recycle key again, otherwise it may cause data loss. **Notice**: There is a compatibility issue with multi-statement transaction write operations during upgrades that could cause write operations to fail either before or during the meta service upgrade process.
…trying prepare rowset (apache#51048) related PR apache#51129
…trying prepare rowset (apache#51048) related PR apache#51129
…for load (apache#51129) (apache#4066) pick from: apache#51129 If the transaction has been finished, it means the prepare/commit rowset is a timeout retry request. In this case, do not write the recycle key again, otherwise it may cause data loss. **Notice**: There is a compatibility issue with multi-statement transaction write operations during upgrades that could cause write operations to fail either before or during the meta service upgrade process.
…trying prepare rowset (apache#51048) (apache#4097) related PR apache#51129
…for load (apache#51129) (apache#4106) pick from: apache#51129 If the transaction has been finished, it means the prepare/commit rowset is a timeout retry request. In this case, do not write the recycle key again, otherwise it may cause data loss. **Notice**: There is a compatibility issue with multi-statement transaction write operations during upgrades that could cause write operations to fail either before or during the meta service upgrade process.
…trying prepare rowset (apache#51048) (apache#4103) related PR apache#51129
What problem does this PR solve?
Issue Number: close #xxx
Related PR: #xxx
Problem Summary:
If the transaction has been finished, it means the prepare/commit rowset is a timeout retry request. In this case, do not write the recycle key again, otherwise it may cause data loss.
Notice:
There is a compatibility issue with multi-statement transaction write operations during upgrades that could cause write operations to fail either before or during the meta service upgrade process.
Release note
None
Check List (For Author)
Test
Behavior changed:
Does this need documentation?
Check List (For Reviewer who merge this PR)