-
Notifications
You must be signed in to change notification settings - Fork 3.7k
[fix](cloud-mow) Should clear GetDeleteBitmapResponse when geting delete bitmap fail and retry #43261
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
…ete bitmap fail and retry
|
Thank you for your contribution to Apache Doris. Since 2024-03-18, the Document has been moved to doris-website. |
|
run buildall |
|
clang-tidy review says "All clean, LGTM! 👍" |
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. |
zhannngchen
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
…ete bitmap fail and retry (#43261) When geting delete bitmap fail, it will retry, howerve the GetDeleteBitmapResponse doesn't clear now, which will lead to the delete bitmap data of last request residual in GetDeleteBitmapResponse and return to be, it a wrong delete bitmap data and may cause be core.
…` 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.
…` 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.
…n geting delete bitmap fail and retry (apache#43297) Cherry-picked from apache#43261 Co-authored-by: huanghaibin <284824253@qq.com>
…g delete bitmap fail and retry (apache#43358) Problem Summary: pr apache#43261 doesn't clear GetDeleteBitmapResponse correctly, this pr fix this problem
…` 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.
When geting delete bitmap fail, it will retry, howerve the GetDeleteBitmapResponse doesn't clear now, which will lead to the delete bitmap data of last request residual in GetDeleteBitmapResponse and return to be, it a wrong delete bitmap data and may cause be core.