[fix](export) fix concurrent modification issue with export job#43051
Merged
morningman merged 1 commit intoapache:masterfrom Nov 1, 2024
Merged
[fix](export) fix concurrent modification issue with export job#43051morningman merged 1 commit intoapache:masterfrom
morningman merged 1 commit intoapache:masterfrom
Conversation
|
Thank you for your contribution to Apache Doris. Since 2024-03-18, the Document has been moved to doris-website. |
Contributor
Author
|
run buildall |
TPC-H: Total hot run time: 40871 ms |
TPC-DS: Total hot run time: 195747 ms |
ClickBench: Total hot run time: 32.75 s |
BePPPower
approved these changes
Nov 1, 2024
Contributor
|
PR approved by anyone and no changes requested. |
morningman
added a commit
that referenced
this pull request
Nov 1, 2024
hubgeter
approved these changes
Nov 1, 2024
wuwenchi
approved these changes
Nov 1, 2024
CalvinKirs
approved these changes
Nov 1, 2024
Contributor
|
PR approved by at least one committer and no changes requested. |
zy-kkk
approved these changes
Nov 1, 2024
github-actions bot
pushed a commit
that referenced
this pull request
Nov 1, 2024
### What problem does this PR solve? Related PR: #42950 Problem Summary: PR #42950 change some logic in ExportJob, by removing the `taskIdToExecutor`, which is a thread safe ConcurrentHashMap. But there is a problem that, when cancelling a export job, it will clear the `jobExecutorList` in ExportJob, and meanwhile, this `jobExecutorList` may being traversed when creating the export job, causing concurrent modification exception. This PR fix it by locking the writeLock of ExportMgr when cancelling the export job.
16 tasks
morningman
added a commit
to morningman/doris
that referenced
this pull request
Nov 6, 2024
…he#43051) ### What problem does this PR solve? Related PR: apache#42950 Problem Summary: PR apache#42950 change some logic in ExportJob, by removing the `taskIdToExecutor`, which is a thread safe ConcurrentHashMap. But there is a problem that, when cancelling a export job, it will clear the `jobExecutorList` in ExportJob, and meanwhile, this `jobExecutorList` may being traversed when creating the export job, causing concurrent modification exception. This PR fix it by locking the writeLock of ExportMgr when cancelling the export job.
morningman
added a commit
that referenced
this pull request
Nov 6, 2024
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What problem does this PR solve?
Related PR: #42950
Problem Summary:
PR #42950 change some logic in ExportJob, by removing the
taskIdToExecutor, which isa thread safe ConcurrentHashMap.
But there is a problem that, when cancelling a export job, it will clear the
jobExecutorListin ExportJob,and meanwhile, this
jobExecutorListmay being traversed when creating the export job,causing concurrent modification exception.
This PR fix it by locking the writeLock of ExportMgr when cancelling the export job.
Check List (For Committer)
Test
Behavior changed:
Does this need documentation?
Release note
None
Check List (For Reviewer who merge this PR)