Uh oh!
There was an error while loading. Please reload this page.
branch-3.0-pick: [Fix](cloud) Should consider tablet state change whether to skip sync_rowsets in publish phase (#48400) - #48667
Conversation
Thearas
commented
Mar 5, 2025
Thank you for your contribution to Apache Doris. Please clearly describe your PR:
|
bobhan1
commented
Mar 5, 2025
run buildall |
doris-robot
commented
Mar 5, 2025
TeamCity cloud ut coverage result: |
bobhan1
commented
Mar 5, 2025
run cloud_p0 |
8ce0f46 to
8a90657Comparebobhan1
commented
Mar 6, 2025
run buildall |
doris-robot
commented
Mar 6, 2025
TeamCity cloud ut coverage result: |
8a90657 to
d2037dbComparedataroaring
commented
Mar 7, 2025
run buildall |
doris-robot
commented
Mar 7, 2025
TeamCity cloud ut coverage result: |
doris-robot
commented
Mar 7, 2025
TPC-H: Total hot run time: 40599 ms |
doris-robot
commented
Mar 7, 2025
TPC-DS: Total hot run time: 197000 ms |
doris-robot
commented
Mar 7, 2025
ClickBench: Total hot run time: 33.32 s |
bobhan1
commented
Mar 7, 2025
run beut |
1 similar comment
bobhan1
commented
Mar 8, 2025
run beut |
…c_rowsets` in publish phase (apache#48400) considering the following situation: 1. heavy SC begins 2. alter task on tablet X(to tablet Y) is sent to be1 3. be1 shutdown for some reason 4. new loads on new tablet Y are routed to be2(which will skip to calculate delete bitmaps in commit phase and publish phase because the tablet's state is `NOT_READY`) 5. be1 restarted and resumed to do alter task 6. alter task on be1 finished and change the tablet's state to `RUNNING` in MS 7. some load on tablet Y on be2 skip to calculate delete bitmap because it doesn't know the tablet's state has changed, which will cause duplicate key problem Like apache#37670, this PR let the meta service return the tablet states along with the getDeleteBitmapUpdateLockResponse to FE and FE will send them to BE to let the BE know whether it should sync_rowsets() due to tablet state change on other BEs.
d2037db to
5e9a40bComparebobhan1
commented
Mar 10, 2025
run buildall |
doris-robot
commented
Mar 10, 2025
TeamCity cloud ut coverage result: |
PR approved by at least one committer and no changes requested. |
PR approved by anyone and no changes requested. |
doris-robot
commented
Mar 10, 2025
TPC-H: Total hot run time: 40403 ms |
doris-robot
commented
Mar 10, 2025
TPC-DS: Total hot run time: 197734 ms |
doris-robot
commented
Mar 10, 2025
ClickBench: Total hot run time: 32.41 s |
pick #48400