[bugfix](asyncwriter) async writer's lock should not include finish or close method#33077
[bugfix](asyncwriter) async writer's lock should not include finish or close method#33077yiguolei merged 2 commits intoapache:masterfrom
Conversation
|
Thank you for your contribution to Apache Doris. Since 2024-03-18, the Document has been moved to doris-website. |
|
run buildall |
1 similar comment
|
run buildall |
|
clang-tidy review says "All clean, LGTM! 👍" |
TPC-H: Total hot run time: 38926 ms |
|
TeamCity be ut coverage result: |
TPC-DS: Total hot run time: 181111 ms |
ClickBench: Total hot run time: 29.87 s |
|
run buildall |
|
clang-tidy review says "All clean, LGTM! 👍" |
|
TeamCity be ut coverage result: |
TPC-H: Total hot run time: 38525 ms |
|
PR approved by at least one committer and no changes requested. |
|
PR approved by anyone and no changes requested. |
TPC-DS: Total hot run time: 181768 ms |
ClickBench: Total hot run time: 30.37 s |
|
Load test result on machine: 'aliyun_ecs.c7a.8xlarge_32C64G' |
…r close method (#33077) close or finish method will take a lot of time, and the lock will hold a lot of time. If there is a bug in close or finish method, it will affect pipeline execute thread. writer's close method will need this lock, so that it will hang when close method is called.
Proposed changes
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...