Skip to content

fix(infra): drop fly idle_timeout 600 -> 120#38

Merged
kevincodex1 merged 1 commit into
mainfrom
infra/fly-idle-timeout
Jun 12, 2026
Merged

fix(infra): drop fly idle_timeout 600 -> 120#38
kevincodex1 merged 1 commit into
mainfrom
infra/fly-idle-timeout

Conversation

@kevincodex1

@kevincodex1 kevincodex1 commented Jun 12, 2026

Copy link
Copy Markdown
Contributor

600s idle windows let hung clients pin Fly proxy connection slots up to hard_limit, which amplified the 2026-06-12 production outage. 120s was deployed there as the fix; carry it into the reference config.

Summary by CodeRabbit

  • Chores
    • Updated server connection handling configuration to improve service reliability and stability.

600s idle windows let hung clients pin Fly proxy connection slots up to
hard_limit, which amplified the 2026-06-12 production outage. 120s was
deployed there as the fix; carry it into the reference config.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
@coderabbitai

coderabbitai Bot commented Jun 12, 2026

Copy link
Copy Markdown

Review Change Stack

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: ca9a26c9-e84e-4b81-844b-4baee637feda

📥 Commits

Reviewing files that changed from the base of the PR and between 6abaf1d and 311272a.

📒 Files selected for processing (1)
  • infra/fly/fly.toml

📝 Walkthrough

Walkthrough

The Fly.io configuration for the gitlawb-node-test app reduces the HTTP service idle timeout from 600 seconds to 120 seconds. Inline comments are updated to explain the rationale: preventing hung clients from pinning connections during long idle windows, informed by a prior production outage.

Changes

Fly.io HTTP Idle Timeout Configuration

Layer / File(s) Summary
HTTP idle timeout adjustment
infra/fly/fly.toml
idle_timeout within http_service.http_options is reduced from 600 to 120 seconds with updated comments referencing prevention of hung clients pinning connections and hard_limit as a root factor in prior production context.

Estimated Code Review Effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Poem

A rabbit hops through config files so fine,
Where idle_timeout shrinks from six to one—
No hanging clients now will hog the line,
Two minutes tops before the timeout's done! 🐰⏱️

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title clearly and specifically describes the main change: reducing the Fly.io idle_timeout configuration value from 600 to 120 seconds.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.

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

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch infra/fly-idle-timeout

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

@kevincodex1 kevincodex1 merged commit a2217bf into main Jun 12, 2026
6 checks passed
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