🐛(scalingo) isolate the metrics endpoint in its own gunicorn pool#776
Open
NathanVss wants to merge 1 commit into
Open
🐛(scalingo) isolate the metrics endpoint in its own gunicorn pool#776NathanVss wants to merge 1 commit into
NathanVss wants to merge 1 commit into
Conversation
DeployCenter calls the usage metrics endpoint synchronously while answering our entitlements requests. Served by the same sync workers, this callback could queue behind the very requests blocked waiting for DeployCenter, freezing the whole pool until timeouts fire. A dedicated single-worker gunicorn behind nginx guarantees the callback always finds a free worker, making the circular wait impossible. The main pool is sized to WEB_CONCURRENCY minus the reserved worker so the container keeps the worker count its size was provisioned for, and both values are logged at boot to ease diagnosing worker starvation.
|
kernicPanel
approved these changes
Jul 22, 2026
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.
DeployCenter calls the usage metrics endpoint synchronously while answering our entitlements requests. Served by the same sync workers, this callback could queue behind the very requests blocked waiting for DeployCenter, freezing the whole pool until timeouts fire. A dedicated single-worker gunicorn behind nginx guarantees the callback always finds a free worker, making the circular wait impossible.
The main pool is sized to WEB_CONCURRENCY minus the reserved worker so the container keeps the worker count its size was provisioned for, and both values are logged at boot to ease diagnosing worker starvation.
This is a first approach solution, with @sylvinus we talked about providing the metrics data directly in the /entitlements calls, avoiding DeployCenter to make a call to drive's /metrics api routes, which would speed up the call and make impossible dead locks.