Skip to content

fix(websocket): tighten upstream WS dead-peer window under ~30s head silence #9

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
snowkide wants to merge 1 commit into from
Closed

fix(websocket): tighten upstream WS dead-peer window under ~30s head silence #9

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 9 additions & 2 deletions clients/ws_json_rpc_client.go
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -41,12 +41,19 @@ const (
// re-dials. wsPongWait must comfortably exceed wsPingInterval so at least
// two pings fit in the window.
//
// Sized so a black-holed upstream is torn down and re-dialed before typical
// downstream head-liveness thresholds (~30s, e.g. Polygon NoNewHeadsThreshold).
// Sticky client WS connections pin one eRPC pod: if that pod's head-feeding
// upstream wedges for wsPongWait, the client sees silence even while other
// pods / HTTP failover still tip. 30s/75s left a ~45s gap where consumers
// marked the gateway unhealthy before we reconnected.
//
// Vars (not consts) so tests can compress time. They are copied into
// per-client fields at construction, so client goroutines never read them
// after NewWsJsonRpcClient returns.
var (
wsPingInterval = 30 * time.Second
wsPongWait = 75 * time.Second
wsPingInterval = 10 * time.Second
wsPongWait = 25 * time.Second
)

// WsJsonRpcClient implements ClientInterface for WebSocket-based JSON-RPC upstream connections.
Expand Down
Loading