Skip to content

Conversation

@bobhan1
Copy link
Contributor

@bobhan1 bobhan1 commented Dec 4, 2024

What problem does this PR solve?

Similar to #43261, GetDeleteBitmapUpdateLockResponse should be cleared after get_delete_bitmap_update_lock fails on MS. Otherwise BE may get staled compaction cnts and wrongly skip to sync rowsets before update_delete_bitmap() thus causing duplicate keys problem.

Check List (For Author)

  • Test

    • 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
  • Behavior changed:

    • No.
    • Yes.
  • Does this need documentation?

    • No.
    • Yes.

Check List (For Reviewer who merge this PR)

  • Confirm the release note
  • Confirm test cases
  • Confirm document
  • Add branch pick label

@doris-robot
Copy link

Thank you for your contribution to Apache Doris.
Don't know what should be done next? See How to process your PR.

Please clearly describe your PR:

  1. What problem was fixed (it's best to include specific error reporting information). How it was fixed.
  2. Which behaviors were modified. What was the previous behavior, what is it now, why was it modified, and what possible impacts might there be.
  3. What features were added. Why was this function added?
  4. Which code was refactored and why was this part of the code refactored?
  5. Which functions were optimized and what is the difference before and after the optimization?

@bobhan1
Copy link
Contributor Author

bobhan1 commented Dec 4, 2024

run buildall

<< " tablet=" << res->tablet_id()
<< " delete_bitmap_count=" << res->segment_delete_bitmaps_size();
} else if constexpr (std::is_same_v<Response, GetDeleteBitmapUpdateLockResponse>) {
if (res->status().code() != MetaServiceCode::OK) {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

better not process rpc content here

Copy link
Contributor

@dataroaring dataroaring left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@github-actions github-actions bot added the approved Indicates a PR has been approved by one committer. label Dec 4, 2024
@github-actions
Copy link
Contributor

github-actions bot commented Dec 4, 2024

PR approved by at least one committer and no changes requested.

@github-actions
Copy link
Contributor

github-actions bot commented Dec 4, 2024

PR approved by anyone and no changes requested.

@dataroaring dataroaring merged commit 00ee11e into apache:master Dec 5, 2024
24 of 26 checks passed
github-actions bot pushed a commit that referenced this pull request Dec 5, 2024
…` when geting delete bitmap update lock fail and retry (#44975)

Similar to #43261,
`GetDeleteBitmapUpdateLockResponse` should be cleared after
`get_delete_bitmap_update_lock` fails on MS. Otherwise BE may get staled
compaction cnts and wrongly skip to sync rowsets before
`update_delete_bitmap()` thus causing duplicate keys problem.
dataroaring pushed a commit that referenced this pull request Dec 5, 2024
…LockResponse` when geting delete bitmap update lock fail and retry #44975 (#45010)

Cherry-picked from #44975

Co-authored-by: bobhan1 <baohan@selectdb.com>
BiteTheDDDDt pushed a commit to BiteTheDDDDt/incubator-doris that referenced this pull request Feb 7, 2025
…` when geting delete bitmap update lock fail and retry (apache#44975)

Similar to apache#43261,
`GetDeleteBitmapUpdateLockResponse` should be cleared after
`get_delete_bitmap_update_lock` fails on MS. Otherwise BE may get staled
compaction cnts and wrongly skip to sync rowsets before
`update_delete_bitmap()` thus causing duplicate keys problem.
@gavinchou gavinchou mentioned this pull request Feb 18, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by one committer. dev/3.0.4-merged p0_w reviewed

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants