Skip to content

Conversation

@github-actions
Copy link
Contributor

Cherry-picked from #41395

Here is an expample while commit rpc will send twice:
1. first commit request try to get delete bitmap lock, there is 2
lock(fe and ms), which take over rpc timeout(60s default) but not send
DELETE_BITMAP_LOCK_ERR to be, and fe will continue to send calculate
delete bitmap task to be
2. be calculate delete bitmap success and remove delete bitmap cache
3. because step 1 take over 60s, be will resend commit rpc to fe
4. after first commit request done, the second commit request from step
3 will do the same thing, but delete bitmap cache has been delete by
first commit, so it will fail on be
5. client will see commit fail

this pr check transaction status before sending delete bitmap task to
be, if transaction status is committed or visible, it no need to
recalculate delete bitmap again, just retrun rpc success to be.
@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?

@doris-robot
Copy link

run buildall

@dataroaring dataroaring reopened this Nov 13, 2024
@dataroaring dataroaring merged commit 69b8e2b into branch-3.0 Nov 13, 2024
@dataroaring dataroaring deleted the auto-pick-41395-branch-3.0 branch November 14, 2024 11:24
@gavinchou gavinchou mentioned this pull request Nov 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants