Skip to content

branch-3.0: [fix](cloud) fix filecache warmup crash due to spurious wakeup #48623 #48654

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.

Sign up for GitHub

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

Jump to bottom
Merged
dataroaring merged 1 commit into from
Mar 10, 2025
Merged

branch-3.0: [fix](cloud) fix filecache warmup crash due to spurious wakeup #48623 #48654

dataroaring merged 1 commit into from
Mar 10, 2025

Conversation

@github-actions
Copy link
Contributor

@github-actions github-actions bot commented Mar 4, 2025

Cherry-picked from #48623

@freemandealer
[fix](cloud) fix filecache warmup crash due to spurious wakeup (#48623)
374d09f 
*** SIGSEGV address not mapped to object (@0x30) received by PID 1379
(TID 1888 OR 0x7fa73d4c8700) from PID 48; stack trace: ***
0# doris::signal::(anonymous namespace)::FailureSignalHandler(int,
siginfo_t*, void*) at
/home/zcp/repo_center/doris_release/doris/be/src/common/signal_handler.h:421
1# PosixSignals::chained_handler(int, siginfo*, void*) [clone .part.0]
in /opt/jdk-17/lib/server/libjvm.so
 2# JVM_handle_linux_signal in /opt/jdk-17/lib/server/libjvm.so
 3# 0x00007FAB4C4ED400 in /lib64/libc.so.6
4# doris::CloudWarmUpManager::handle_jobs() at
/home/zcp/repo_center/doris_release/doris/be/src/cloud/cloud_warm_up_manager.cpp:73

_pending_job_metas may wake up with empty, i.e. spurious wakeup
@github-actions github-actions bot requested a review from dataroaring as a code owner March 4, 2025 15:35
@Thearas
Copy link
Contributor

Thearas commented Mar 4, 2025

Thank you for your contribution to Apache Doris.
Don't know what should be done next? See How to process your PR.

Please clearly describe your PR:

  1. What problem was fixed (it's best to include specific error reporting information). How it was fixed.
  2. Which behaviors were modified. What was the previous behavior, what is it now, why was it modified, and what possible impacts might there be.
  3. What features were added. Why was this function added?
  4. Which code was refactored and why was this part of the code refactored?
  5. Which functions were optimized and what is the difference before and after the optimization?

@dataroaring dataroaring closed this Mar 4, 2025
@dataroaring dataroaring reopened this Mar 4, 2025
@Thearas
Copy link
Contributor

Thearas commented Mar 4, 2025

run buildall

dataroaring
dataroaring approved these changes Mar 10, 2025
View reviewed changes
Copy link
Contributor

@dataroaring dataroaring left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@github-actions github-actions bot added the approved Indicates a PR has been approved by one committer. label Mar 10, 2025
@github-actions
Copy link
Contributor Author

github-actions bot commented Mar 10, 2025

PR approved by at least one committer and no changes requested.

@github-actions
Copy link
Contributor Author

github-actions bot commented Mar 10, 2025

PR approved by anyone and no changes requested.

@dataroaring dataroaring merged commit 5dfcabf into branch-3.0 Mar 10, 2025
21 of 24 checks passed
@github-actions github-actions bot deleted the auto-pick-48623-branch-3.0 branch March 10, 2025 06:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@dataroaring dataroaring dataroaring approved these changes

Assignees

No one assigned

Labels

approved Indicates a PR has been approved by one committer. reviewed

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

3 participants

@Thearas @dataroaring @freemandealer