fix: add maxTotalSockets to prevent socket exhaustion across IPv4/IPv6 - #156
Merged
Conversation
The previous fix with maxSockets only limited connections per-host, but Railway's internal DNS returns both IPv4 and IPv6 addresses which are treated as separate hosts. This caused connections to grow unbounded. Adding maxTotalSockets: 50 limits total connections across ALL hosts, properly preventing socket exhaustion in dual-stack environments. Changes: - Add maxTotalSockets: 50 to all http.Agent instances - Remove deprecated timeout option from http.Agent - Bump SDK version to 0.1.35 - Update init-example to use 0.1.35 Co-Authored-By: Claude <noreply@anthropic.com>
Contributor
Performance
✓ No regressions detected |
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
1 participant
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.
Summary
maxTotalSockets: 50to limit total connections across ALL hostsRoot Cause
maxSockets: 10only limits connections per-host, but IPv4 and IPv6 addresses are treated as different hosts by Node.js http.Agent. This caused unbounded connection growth (28k+ connections in 10 minutes).Changes
maxTotalSockets: 50to all http.Agent instancestimeoutoption from http.AgentTest plan
cat /proc/net/sockstat🤖 Generated with Claude Code