Skip to content

fix: kong stops responding#4857

Open
unlair wants to merge 2 commits intosupabase:developfrom
unlair:fix/kong-stops-responding
Open

fix: kong stops responding#4857
unlair wants to merge 2 commits 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.

Summary by CodeRabbit

  • Chores
    • Removed a hardcoded worker process setting from Kong container configuration, allowing the system to use default resource allocation.

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 requested a review from a team as a code owner February 15, 2026 04:37
@coderabbitai
Copy link

coderabbitai bot commented Feb 15, 2026

📝 Walkthrough

Walkthrough

A single environment variable (KONG_NGINX_WORKER_PROCESSES=1) was removed from the Kong container configuration in the start.go file. This one-line deletion alters how Kong's Nginx worker processes are configured when the container is instantiated.

Changes

Cohort / File(s) Summary
Kong Configuration
internal/start/start.go
Removed KONG_NGINX_WORKER_PROCESSES=1 environment variable from Kong container setup.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

🚥 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.

✨ Finishing touches
  • 📝 Generate docstrings
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment

No actionable comments were generated in the recent review. 🎉


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

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.

2 participants

Comments