-
Notifications
You must be signed in to change notification settings - Fork 3.7k
[fix](cloud) fix filecache warmup crash due to memory corruption #52394
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
Conversation
|
Thank you for your contribution to Apache Doris. Please clearly describe your PR:
|
|
run buildall |
|
@freemandealer can review? |
BE UT Coverage ReportIncrement line coverage Increment coverage report
|
|
run buildall |
TPC-H: Total hot run time: 34316 ms |
TPC-DS: Total hot run time: 185702 ms |
ClickBench: Total hot run time: 29.39 s |
BE UT Coverage ReportIncrement line coverage Increment coverage report
|
|
We're closing this PR because it hasn't been updated in a while. |
What problem does this PR solve?
Issue Number: close #xxx
Related PR: #48623 #43262
Problem Summary:
A coredump may occur in the BE when manually canceling a running warm-up task, or when the BE restarts during warm-up and creates a new warm-up task.
The coredump is caused by the clear_job function clearing _pending_job_metas, while another thread simultaneously calls _pending_job_metas.pop_front(), leading to undefined behavior due to memory corruption. If the _pending_job_metas is accessed again afterward, it may trigger a coredump.
Release note
None
Check List (For Author)
Test
cancel a running warm-up task or restarts during warm-up and creates a new warm-up task
Behavior changed:
Does this need documentation?
Check List (For Reviewer who merge this PR)