-
Notifications
You must be signed in to change notification settings - Fork 3.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Fix](JobManager)Release the lock immediately after modifying job metadata to avoid holding the lock for an extended period. #38162
Conversation
Thank you for your contribution to Apache Doris. Since 2024-03-18, the Document has been moved to doris-website. |
run buildall |
TPC-H: Total hot run time: 39899 ms
|
TPC-DS: Total hot run time: 174144 ms
|
ClickBench: Total hot run time: 30.91 s
|
…adata to avoid holding the lock for an extended period.
1ab1d57
to
a5960cf
Compare
run buildall |
PR approved by at least one committer and no changes requested. |
PR approved by anyone and no changes requested. |
TPC-H: Total hot run time: 39693 ms
|
TPC-DS: Total hot run time: 173791 ms
|
ClickBench: Total hot run time: 30.58 s
|
…adata to avoid holding the lock for an extended period.
…-lock # Conflicts: # fe/fe-core/src/main/java/org/apache/doris/job/manager/JobManager.java
run buildall |
…adata to avoid holding the lock for an extended period.apache#38162
TPC-H: Total hot run time: 39981 ms
|
TPC-DS: Total hot run time: 174487 ms
|
ClickBench: Total hot run time: 30.74 s
|
PR approved by at least one committer and no changes requested. |
run cloud_p0 |
1 similar comment
run cloud_p0 |
…adata to avoid holding the lock for an extended period. (#38162) ## Proposed changes When deleting a job in MV, a DB lock is held. However, due to the larger lock granularity of the Job Manager, this may prevent obtaining the lock. This issue arises because during the creation of a job, immediately scheduled tasks need to perform their initial scheduling and compensate for tasks within the time window. To alleviate this issue, we are attempting to reduce the lock granularity. <!--Describe your changes.-->
Proposed changes
When deleting a job in MV, a DB lock is held. However, due to the larger lock granularity of the Job Manager, this may prevent obtaining the lock. This issue arises because during the creation of a job, immediately scheduled tasks need to perform their initial scheduling and compensate for tasks within the time window. To alleviate this issue, we are attempting to reduce the lock granularity.