-
Notifications
You must be signed in to change notification settings - Fork 3.7k
branch-3.0: [Fix](Compaction) Cumulative Points Not Incrementing After Delete Operation #47282 #49732
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
…ration (#47282) When a tablet's first rowset is a delete operation followed by data rowsets, the cumulative compaction process currently skips the delete rowset and only compacts the subsequent data rowsets. This leads to a failure in incrementing the cumulative point due to the condition output_rowset->start_version() == last_cumulative_point not being satisfied. In the current behavior, the cumulative point for the delete rowset only advances after all data rowsets have completed cumulative compaction. This creates an inefficient scenario where if continuous data ingestion occurs, all subsequent data rowsets are forced to participate in cumulative compaction, resulting in significant resource waste. This PR fixes the issue by properly handling the cumulative point advancement when encountering delete rowsets at the beginning of the version sequence.
|
Thank you for your contribution to Apache Doris. Please clearly describe your PR:
|
|
run buildall |
TPC-H: Total hot run time: 40283 ms |
TPC-DS: Total hot run time: 197238 ms |
ClickBench: Total hot run time: 32.45 s |
BE UT Coverage ReportIncrement line coverage Increment coverage report
|
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
|
PR approved by at least one committer and no changes requested. |
|
PR approved by anyone and no changes requested. |
Cherry-picked from #47282