fix: Prevent Agent from crashing under heavy and time consuming CPU Workloads.#286
Open
zvigrinberg wants to merge 1 commit into
Open
fix: Prevent Agent from crashing under heavy and time consuming CPU Workloads.#286zvigrinberg wants to merge 1 commit into
zvigrinberg wants to merge 1 commit into
Conversation
…s under heavy CPU load The Python event loop (GIL-bound) cannot serve HTTP /health responses when the CPU is saturated by concurrent workloads, causing the httpGet liveness probe to fail repeatedly and triggering pod restarts. The exec probe checks that PID 1 is still alive via /proc/1/status, which runs outside the Python process and is unaffected by event loop stalls.
Collaborator
✅ Snyk checks have passed. No issues have been found so far.
💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse. |
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
2 participants
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.
fix: switch liveness probe from httpGet to exec to prevent pod crashe…
The Python event loop (GIL-bound) cannot serve HTTP /health responses when the CPU is saturated by heavy longterm concurrent workloads, causing the httpGet liveness probe to fail repeatedly and triggering pod restarts. The exec probe checks that PID 1 is still alive via /proc/1/status, which runs outside the Python process and is unaffected by event loop stalls.
This is as good as it gets for now, to make sure the agent pod process is not turning into a zombie process....
Just at least up until the agent will be upgraded to python 3.14.6 that freed from GIL restriction and enables a better concurrency model and true parallalism