Skip to content

fix: kong stops responding#4857

Open
unlair wants to merge 1 commit intosupabase:developfrom
unlair:fix/kong-stops-responding
Open

fix: kong stops responding#4857
unlair wants to merge 1 commit intosupabase:developfrom
unlair:fix/kong-stops-responding

Conversation

@unlair
Copy link

@unlair unlair commented Feb 15, 2026

kong easily gets overwhelmed when receiving many requests, resulting in an error complaining about not having enough workers. This was due to KONG_NGINX_WORKER_PROCESSES=1 being set. Kong automatically determins the right number of worker processes when this is not specified, which resolves the issue.

What kind of change does this PR introduce?

Bug fix (removing a bad env var for the Kong container).

What is the current behavior?

If many parallel requests are made to the Storage API, Kong will quickly stop responding and start terminating socket connections.

What is the new behavior?

Kong is able to handle many parallel connections without choking.

@unlair unlair requested a review from a team as a code owner February 15, 2026 04:37
@coderabbitai
Copy link

coderabbitai bot commented Feb 15, 2026

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

Configuration used: Central YAML (base), Organization UI (inherited)

Review profile: CHILL

Plan: Pro

Cache: Disabled due to Reviews > Disable Cache setting

Disabled knowledge base sources:

  • Linear integration is disabled

You can enable these sources in your CodeRabbit configuration.

📥 Commits

Reviewing files that changed from the base of the PR and between de11898 and a2916f7.

📒 Files selected for processing (1)
  • internal/start/start.go
💤 Files with no reviewable changes (1)
  • internal/start/start.go

📝 Walkthrough

Summary by CodeRabbit

  • Chores
    • Removed a fixed worker process configuration from the Kong container environment, allowing it to use default settings.

Walkthrough

Removed the environment variable KONG_NGINX_WORKER_PROCESSES=1 from the Kong container configuration in internal/start/start.go. This one-line deletion changes the environment passed to the Kong container at startup.

Sequence Diagram(s)

🚥 Pre-merge checks | ✅ 4
✅ Passed checks (4 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title accurately describes the main change: removing a problematic environment variable that was causing Kong to stop responding under load.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Merge Conflict Detection ✅ Passed ✅ No merge conflicts detected when merging into develop

✏️ Tip: You can configure your own custom pre-merge checks in the settings.


Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

kong easily gets overwhelmed when receiving many requests, resulting in an error complaining about not having enough workers. This was due to KONG_NGINX_WORKER_PROCESSES=1 being set. Kong automatically determins the right number of worker processes when this is not specified, which resolves the issue.
@unlair unlair force-pushed the fix/kong-stops-responding branch from c8db24d to a2916f7 Compare February 28, 2026 01:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant