-
Notifications
You must be signed in to change notification settings - Fork 3.9k
[test](pipeline) collect Cloud P0 resource usage #65125
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
Merged
hello-stephen
merged 1 commit into
apache:master
from
shuke987:add-cloud-p0-resource-monitor
Jul 3, 2026
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
stop_system_resource_monitoronly kills and waits for the monitor subshell, but the loop is often blocked in its foregroundsleep "${interval}"child. I can reproduce this withSYSTEM_RESOURCE_MONITOR_INTERVAL_SECONDS=123: before stop the monitor ownssleep 123, and after this function returns the monitor PID is gone but that sleep is still alive with PPID 1. In the normal Cloud P0 path this leaves a straysleep 60after cleanup, and a custom interval can leave it around much longer. Please have the monitor worker clean up its active child on TERM, or stop the whole monitor process tree/process group, before reporting that the monitor has stopped.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fixed in 0f7197f. The monitor worker now tracks the active sleep child and kills/waits it from a TERM/INT cleanup trap before exiting.