Uh oh!
There was an error while loading. Please reload this page.
[Fix](rowset) When a rowset is cooled down, it is directly deleted. This can result in data query misses in the second phase of a two-phase query. - #21741
Conversation
eldenmoon
commented
Jul 12, 2023
run buildall |
eldenmoon
commented
Jul 12, 2023
run buildall |
clang-tidy review says "All clean, LGTM! 👍" |
1 similar comment
clang-tidy review says "All clean, LGTM! 👍" |
eldenmoon
commented
Jul 12, 2023
run buildall |
clang-tidy review says "All clean, LGTM! 👍" |
hello-stephen
commented
Jul 12, 2023
(From new machine)TeamCity pipeline, clickbench performance test result: |
hello-stephen
commented
Jul 12, 2023
(From new machine)TeamCity pipeline, clickbench performance test result: |
hello-stephen
commented
Jul 12, 2023
TeamCity pipeline, clickbench performance test result: |
hello-stephen
commented
Jul 12, 2023
TeamCity pipeline, clickbench performance test result: |
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
eldenmoon
commented
Jul 12, 2023
run buildall |
clang-tidy review says "All clean, LGTM! 👍" |
1 similar comment
clang-tidy review says "All clean, LGTM! 👍" |
eldenmoon
commented
Jul 12, 2023
run buildall |
clang-tidy review says "All clean, LGTM! 👍" |
hello-stephen
commented
Jul 12, 2023
(From new machine)TeamCity pipeline, clickbench performance test result: |
hello-stephen
commented
Jul 12, 2023
(From new machine)TeamCity pipeline, clickbench performance test result: |
hello-stephen
commented
Jul 12, 2023
TeamCity pipeline, clickbench performance test result: |
Uh oh!
There was an error while loading. Please reload this page.
eldenmoon
commented
Jul 12, 2023
run buildall |
clang-tidy review says "All clean, LGTM! 👍" |
PR approved by anyone and no changes requested. |
hello-stephen
commented
Jul 12, 2023
(From new machine)TeamCity pipeline, clickbench performance test result: |
…his can result in data query misses in the second phase of a two-phase query. related pr apache#20732 There are two reasons for moving the logic of delayed deletion from the Tablet to the StorageEngine. The first reason is to consolidate the logic and unify the delayed operations. The second reason is that delayed garbage collection during queries can cause rowsets to remain in the "stale rowsets" state, preventing the timely deletion of rowset metadata, It may cause rowset metadata too large.
eldenmoon
commented
Jul 12, 2023
run buildall |
clang-tidy review says "All clean, LGTM! 👍" |
hello-stephen
commented
Jul 12, 2023
(From new machine)TeamCity pipeline, clickbench performance test result: |
…his can result in data query misses in the second phase of a two-phase query. (#21741) * [Fix](rowset) When a rowset is cooled down, it is directly deleted. This can result in data query misses in the second phase of a two-phase query. related pr #20732 There are two reasons for moving the logic of delayed deletion from the Tablet to the StorageEngine. The first reason is to consolidate the logic and unify the delayed operations. The second reason is that delayed garbage collection during queries can cause rowsets to remain in the "stale rowsets" state, preventing the timely deletion of rowset metadata, It may cause rowset metadata too large. * not use unused rowsets
…his can result in data query misses in the second phase of a two-phase query. (apache#21741) * [Fix](rowset) When a rowset is cooled down, it is directly deleted. This can result in data query misses in the second phase of a two-phase query. related pr apache#20732 There are two reasons for moving the logic of delayed deletion from the Tablet to the StorageEngine. The first reason is to consolidate the logic and unify the delayed operations. The second reason is that delayed garbage collection during queries can cause rowsets to remain in the "stale rowsets" state, preventing the timely deletion of rowset metadata, It may cause rowset metadata too large. * not use unused rowsets
TsukiokaKogane
commented
Mar 8, 2024
this pr could cause unused rowset not gc, fixed in #30904 |
Proposed changes
related pr #20732
There are two reasons for moving the logic of delayed deletion from the Tablet to the StorageEngine. The first reason is to consolidate the logic and unify the delayed operations. The second reason is that delayed garbage collection during queries can cause rowsets to remain in the "stale rowsets" state, preventing the timely deletion of rowset metadata, It may cause rowset metadata too large.
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...