[fix](merge-on-write) remove some CHECKs in Tablet::revise_tablet_meta#31268
Conversation
|
Thank you for your contribution to Apache Doris. |
|
clang-tidy review says "All clean, LGTM! 👍" |
1 similar comment
|
clang-tidy review says "All clean, LGTM! 👍" |
|
clang-tidy review says "All clean, LGTM! 👍" |
b7267d2 to
ca1851d
Compare
|
clang-tidy review says "All clean, LGTM! 👍" |
ca1851d to
f60697e
Compare
| DBUG_EXECUTE_IF("Tablet.update_delete_bitmap_without_lock.random_failed", { | ||
| if (rand() % 100 < (100 * dp->param("percent", 0.1))) { | ||
| LOG_WARNING("Tablet.update_delete_bitmap_without_lock.random_failed"); | ||
| Status BaseTablet::update_delete_bitmap_without_lock( |
There was a problem hiding this comment.
warning: method 'update_delete_bitmap_without_lock' can be made static [readability-convert-member-functions-to-static]
| Status BaseTablet::update_delete_bitmap_without_lock( | |
| static Status BaseTablet::update_delete_bitmap_without_lock( |
|
run buildall |
|
clang-tidy review says "All clean, LGTM! 👍" |
TPC-DS: Total hot run time: 183936 ms |
|
TeamCity be ut coverage result: |
|
PR approved by at least one committer and no changes requested. |
|
PR approved by anyone and no changes requested. |
…_meta (#31268) (#34702) ## Proposed changes Issue Number: close #xxx cherry-pick #31268 ## Further comments If this is a relatively large or complex change, kick off the discussion at [dev@doris.apache.org](mailto:dev@doris.apache.org) by explaining why you chose the solution you did and what alternatives you considered, etc...
…_meta (apache#31268) (apache#34702) ## Proposed changes Issue Number: close #xxx cherry-pick apache#31268 ## Further comments If this is a relatively large or complex change, kick off the discussion at [dev@doris.apache.org](mailto:dev@doris.apache.org) by explaining why you chose the solution you did and what alternatives you considered, etc...
…ur (#37001) ## Proposed changes Issue Number: close #xxx introduced by #31268 full clone failure may produce duplicate keys in mow table the bug would be triggered in the following condition: 1. replica 0 miss version 2. replica 0 try to do full clone from other replicas 3. the full clone failed and the delete bitmap is overrided incorrectly 4. replica 0 try to do incremental clone again and this time the clone succeed 5. incremental clone can't fix the delete bitmap overrided by previous failed full clone 6. duplicate key occurred solution: for full clone, don't override the delete bitmap, use `merge()` method instead.
…ur (#37001) ## Proposed changes Issue Number: close #xxx introduced by #31268 full clone failure may produce duplicate keys in mow table the bug would be triggered in the following condition: 1. replica 0 miss version 2. replica 0 try to do full clone from other replicas 3. the full clone failed and the delete bitmap is overrided incorrectly 4. replica 0 try to do incremental clone again and this time the clone succeed 5. incremental clone can't fix the delete bitmap overrided by previous failed full clone 6. duplicate key occurred solution: for full clone, don't override the delete bitmap, use `merge()` method instead.
…ur (apache#37001) ## Proposed changes Issue Number: close #xxx introduced by apache#31268 full clone failure may produce duplicate keys in mow table the bug would be triggered in the following condition: 1. replica 0 miss version 2. replica 0 try to do full clone from other replicas 3. the full clone failed and the delete bitmap is overrided incorrectly 4. replica 0 try to do incremental clone again and this time the clone succeed 5. incremental clone can't fix the delete bitmap overrided by previous failed full clone 6. duplicate key occurred solution: for full clone, don't override the delete bitmap, use `merge()` method instead.
…ur (apache#37001) ## Proposed changes Issue Number: close #xxx introduced by apache#31268 full clone failure may produce duplicate keys in mow table the bug would be triggered in the following condition: 1. replica 0 miss version 2. replica 0 try to do full clone from other replicas 3. the full clone failed and the delete bitmap is overrided incorrectly 4. replica 0 try to do incremental clone again and this time the clone succeed 5. incremental clone can't fix the delete bitmap overrided by previous failed full clone 6. duplicate key occurred solution: for full clone, don't override the delete bitmap, use `merge()` method instead.
Proposed changes
Issue Number: close #xxx
Further comments
If this is a relatively large or complex change, kick off the discussion at dev@doris.apache.org by explaining why you chose the solution you did and what alternatives you considered, etc...