Uh oh!
There was an error while loading. Please reload this page.
[fix](cooldown) Fix potential data loss when clone task's dst tablet is cooldown replica - #17644
Conversation
clang-tidy review says "All clean, LGTM! 👍" |
platoneko
commented
Mar 13, 2023
run beut |
platoneko
commented
Mar 13, 2023
run feut |
platoneko
commented
Mar 13, 2023
run p0 |
platoneko
commented
Mar 13, 2023
run clickbench |
dataroaring
commented
Mar 19, 2023
run buildall |
952b095 to
5305f10Compareplatoneko
commented
Mar 19, 2023
run buildall |
clang-tidy review says "All clean, LGTM! 👍" |
TeamCity pipeline, clickbench performance test result: |
5305f10 to
7780330Compareclang-tidy review says "All clean, LGTM! 👍" |
xiaokang
commented
Aug 24, 2023
run buildall |
dataroaring
commented
Aug 27, 2023
run buildall |
PR approved by at least one committer and no changes requested. |
PR approved by anyone and no changes requested. |
clang-tidy review says "All clean, LGTM! 👍" |
clang-tidy review says "All clean, LGTM! 👍" |
xiaokang
commented
Aug 27, 2023
run buildall |
platoneko
commented
Sep 1, 2023
run buildall |
1 similar comment
platoneko
commented
Sep 1, 2023
run buildall |
clang-tidy review says "All clean, LGTM! 👍" |
1477542 to
6a455f7Compareplatoneko
commented
Sep 1, 2023
run buildall |
clang-tidy review says "All clean, LGTM! 👍" |
hello-stephen
commented
Sep 1, 2023
(From new machine)TeamCity pipeline, clickbench performance test result: |
PR approved by at least one committer and no changes requested. |
…is cooldown replica (#17644) Co-authored-by: Yongqiang YANG <98214048+dataroaring@users.noreply.github.com> Co-authored-by: Kang <kxiao.tiger@gmail.com>
Proposed changes
Issue Number: close #xxx
Problem summary
If this replica is cooldown replica, MUST generate a new
cooldown_meta_idto avoid usecooldown_meta_idgenerated in old cooldown term which may lead to such situation:Replica A is cooldown replica, cooldown_meta_id=2,
Replica B: cooldown_replica=A, cooldown_meta_id=1
Replica A: full clone Replica B, cooldown_meta_id=1, but remote cooldown_meta is still with cooldown_meta_id=2
After tablet report. FE finds all replicas' cooldowned data is consistent(cooldown_meta_id=1)
Replica A: confirm_unused_remote_files, delete some cooldowned data of cooldown_meta_id=2
Replica B: follow_cooldown_data, cooldown_meta_id=2, data lost
Checklist(Required)
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...